Sometimes when using the REST API to retrieve the latest metadata of a specific queue message, it may return ledgerId: -1 and entryId: -1. For example, using the link http://pulsar-broker.mid-pulsar.svc.cluster.local:8080/admin/v2/persistent/rocketmq/MQ_INST_xYww/test-partition-0/lastMessageId. #22455
Unanswered
YANGJINJUE
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Sometimes when using the REST API to retrieve the latest metadata of a specific queue message, it may return ledgerId: -1 and entryId: -1. For example, using the link http://pulsar-broker.mid-pulsar.svc.cluster.local:8080/admin/v2/persistent/rocketmq/MQ_INST_xYww/test-partition-0/lastMessageId.
Then, when trying to access this link with ledgerId: -1 and entryId: -1, it will block indefinitely until timeout at http://pulsar-broker.mid-pulsar.svc.cluster.local:8080/admin/v2/persistent/rocketmq/MQ_INST_xYww/test-partition-0/ledger/-1/entry/-1.
Beta Was this translation helpful? Give feedback.
All reactions