GitHub user visortelle edited a comment on the discussion: Bookie handle is not available - ledger=22 - operation=Failed to read entry - entry=0
It looks like I don't experience this issue anymore. I applied a few fixes for the current issue and a few similar issues. I'm not sure which fix resolved this specific issue. All the issues were flaky in my case: - I started to ensure that I gracefully stopped all the producers and consumers before stopping the Pulsar Standalone instance. - Before the next start, I remove RocksDB and Bookkeeper LOCK files if exist. - I started to avoid creating and modifying resources with the admin API in parallel: https://github.com/apache/pulsar/issues/15896#issuecomment-1951427536 I think it's how Pulsar Standalone should work, but for my use case, this is fine. GitHub link: https://github.com/apache/pulsar/discussions/20985#discussioncomment-8851425 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
