GitHub user haithir added a comment to the discussion: Does tiered storage
offloading change message IDs?
@lhotari
We found the following errors in the Pulsar logs after trying to seek to a
stored message ID and read from there:
`2024-11-22T10:48:14,500+0000 [BookKeeperClientWorker-OrderedExecutor-0-0]
ERROR org.apache.bookkeeper.client.PendingReadOp - Read of ledger entry failed:
L53035749 E0-E0, Sent to
[pulsar-bookie-6.pulsar-bookie.pulsar.svc.cluster.local:3181,
pulsar-bookie-4.pulsar-bookie.pulsar.svc.cluster.local:3181,
pulsar-bookie-3.pulsar-bookie.pulsar.svc.cluster.local:3181], Heard from [] :
bitset = {}, Error = 'No such ledger exists on Bookies'. First unread entry is
(-1, rc = null)
2024-11-22T10:48:14,500+0000 [BookKeeperClientWorker-OrderedExecutor-0-0] WARN
org.apache.bookkeeper.mledger.impl.OpReadEntry -
[ericsson-dev/check-archive/persistent/metadata][reader-b24c841fba] read failed
from ledger at position:53035749:0
org.apache.bookkeeper.mledger.ManagedLedgerException$LedgerNotExistException:
No such ledger exists on Bookies`
The data there exists. After throwing away the stored message ID, we could read
it again.
We have S3 offloading enabled and thought it may be related to this and maybe
happens if the ledger is removed for the offloaded data.
Is this an error or are there expected scenarios where message IDs become
invalid?
GitHub link:
https://github.com/apache/pulsar/discussions/23630#discussioncomment-11369965
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
