@RunLLM rg.apache.pulsar.broker.service.persistent.PersistentDispatcherSingleActiveConsumer - [persistent://public/default/__change_events / reader-b020b2575f-Consumer{subscription=PersistentSubscription{topic=persistent://public/default/__change_events, name=reader-b020b2575f}, consumerId=1, consumerName=8808e, address=/x.x.x.x:35878}] Error reading entries at 3063172:0 : java.util.concurrent.CompletionException: org.apache.bookkeeper.client.BKException$BKNoSuchLedgerExistsOnMetadataServerException: No such ledger exists on Metadata Server - Retrying to read in 15.0 seconds

This error means the Pulsar broker is trying to read a ledger (ID 3063172) that is referenced in metadata (ZooKeeper), but BookKeeper reports that the ledger does not exist on the metadata server. This typically happens if the ledger was deleted or lost, but the Pulsar metadata still references it, causing repeated read failures and retries every 15 seconds. To detect and resolve such inconsistencies, use the PCK tool to check for missing ledgers and clean up orphaned or missing ledger references in metadata. For more details on how to use PCK for this scenario, see PCK Overview and PCK Tutorial. Would you like step-by-step instructions for using PCK to resolve this? Sources: - PCK Tutorial 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@RunLLM Line 464: 2025-11-14T115245,792 [metadata-store-10-1] ERROR org.apache.bookkeeper.meta.CleanupLedgerManager - Failed on operating ledger metadata: -25 Line 541: 2025-11-14T115245,899 [broker-topic-workers-OrderedExecutor-3-0] ERROR org.apache.pulsar.broker.service.persistent.PersistentDispatcherSingleActiveConsumer - [persistent://public/default/__change_events / reader-b020b2575f-Consumer{subscription=PersistentSubscription{topic=persistent://public/default/__change_events

The error code -25 (

BKNoSuchLedgerExistsOnMetadataServerException

) means BookKeeper could not find the ledger metadata in ZooKeeper, but Pulsar is still referencing it. This results in repeated read failures for the

__change_events

system topic, as seen in your logs. This is a known issue when ledgers are deleted or lost but metadata is not updated. Use the PCK tool to detect and clean up missing or orphaned ledgers as described in the PCK Overview and PCK Tutorial. Would you like detailed steps for running PCK to fix this? Sources: - PCK Tutorial 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.