xiaolong ran

ping @zzzming Can you check @EronWright comments? thanks.

The Logic LGTM +1, as @cckellogg said, maybe we can add a new API for this change, e.g: ``` BeforeSendWithContext(ctx context.Context, producer Producer, message *ProducerMessage) ```

> > ``` > > BeforeSendWithContext(ctx context.Context, producer Producer, message *ProducerMessage) > > ``` > > Adding a new function to the interface will still be a breaking change. Applications...

We encountered the same problem. When the AutoRecovery service is started with Bookie, it will find that the current Ledger ID has been deleted, but does Auto Recovery have no...

``` 12:42:41.841 [main-EventThread] INFO org.apache.bookkeeper.meta.ZkLedgerUnderreplicationManager - Latch countdown due to ZK event: WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/ledgers/underreplication/locks 12:42:41.846 [BookieReadThreadPool-OrderedExecutor-0-0] ERROR org.apache.bookkeeper.proto.ReadLacProcessorV3 - No ledger found while performing readLac from ledger: 8049631...

``` 16:02:17.008 [main] INFO org.apache.bookkeeper.tools.cli.commands.client.LedgerMetaDataCommand - ledgerID: 8049631 16:02:17.015 [main] INFO org.apache.bookkeeper.tools.cli.commands.client.LedgerMetaDataCommand - LedgerMetadata{formatVersion=3, ensembleSize=4, writeQuorumSize=3, ackQuorumSize=2, state=OPEN, digestType=CRC32C, password=base64:, ensembles={0=[xxxx]}, customMetadata={component=base64:bWFuYWdlZC1sZWRnZXI=, pulsar/managed-ledger=base64:cHVsc2FxxxxGl0bG9nX2ZpbmRlci1wYXJ0aXRpb24tMjk=, application=base64:cHVsc2Fy}} ```

If you want to directly perform the seek operation on a partitioned topic, you can refer to the behavior here. https://github.com/apache/pulsar-client-go/pull/782

ping @eolivelli PTAL again, thanks

> there were multiple changes around RocksDb. Please try upgrading to BK 4.14.x (this should be easier than upgrade to 4.15). Thanks @dlg99 feedback, we are trying to upgrade Bookie...

Unfortunately, we did not observe in this exception stack, where exactly the call caused Bookie to directly overflow the memory. In a production environment, this happens all of a sudden...