Zixuan Liu

Fix: SendAsync callback was not invoked when producer is in reconnecting

2

Fixes #1332 ### Motivation When the producer reconnects, the batching/non-batching messages can not be added to the pending queue, so the timeout error can not be triggered. This leads to...

refactor: Eliminate redundant cleanup logic in entry log extraction

5

### Motivation The purpose of `extractMetaFromEntryLogs` is to extract metadata, not perform garbage collection. The logic for removing entry logs with no active ledgers is handled separately in `doGcEntryLogs()`. ###...

**FEATURE REQUEST** 1. Please describe the feature you are requesting. Currently, BookKeeper's internal garbage collection (GC) processes (e.g., ledger GC, entry log compaction) run periodically and can also be manually...

[improve][broker] PIP-433: Ensure topic creation before starting GEO

1

PIP: #24485 ### Motivation In a GEO replication scenario, if the remote cluster does not have the replicated topic and the auto-creation type differs between the local and remote clusters,...

### Motivation In geo, the `msgOut` is inaccurate: 1. When `Entry` is batch message, the `org.apache.pulsar.common.stats.Rate#countAdder` and `org.apache.pulsar.common.stats.Rate#totalCountAdder` increment only once. 2. When the network fails, the `org.apache.pulsar.common.stats.Rate#recordEvent(long)` shouldn't be...

[fix][broker] Fix NamespaceService#getListOfNonPersistentTopics not found the topic

2

### Motivation When using the admin-client to set the replication cluster for non-persistent partitioned topic, the broker throws the topic not found, due to `org.apache.pulsar.broker.namespace.NamespaceService#getListOfNonPersistentTopics` didn't fetch the non-persistent partitioned...