GitHub user lhotari added a comment to the discussion: Does tiered storage offloading change message IDs?
> Is this an error or are there expected scenarios where message IDs become > invalid? @haithir There have been some rare bugs in Pulsar and BookKeeper in the past where invididual entries get corrupted already in writing and become unreadable. That's why running on [a recent supported and maintained version](https://pulsar.apache.org/download/) is important for stability. Another reason could be a case where bookies fail and the cluster doesn't have sufficient replication level to recover. That's why running with at least 2 replicates (E=2,Qw=2,Qa=2) is recommended and paying attention to the bookie [autorecovery](https://bookkeeper.apache.org/docs/admin/autorecovery) state. It always possible that there are also unresolved bugs that lead to transient errors where reading an entry fails. Which Pulsar version do you use? GitHub link: https://github.com/apache/pulsar/discussions/23630#discussioncomment-11414388 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
