Wenzhi Feng
Wenzhi Feng
### Motivation the prompt message is wrong. ### Modifications change the prompted message.
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation i find that method getBundleStats return member lastStats,causing duplicate data stored in ZK...
### Motivation Max read position is before the first ongoing txn's position. But the entry id of the first message may be 0, calculate the max read position by `entry...
### Motivation This PR https://github.com/apache/pulsar/pull/17573 has fixed cases that consumer commit offset periodically. It update `lastActive` field of cursor when consumer commit the offset. But there is still corner case...
Fixes https://github.com/apache/pulsar/issues/21968 ### Motivation The implementation of `org.apache.pulsar.broker.service.persistent.PersistentTopic#getLastMessageId` is not consistent with `org.apache.pulsar.broker.service.ServerCnx#handleGetLastMessageId`, for example, `ServerCnx#handleGetLastMessageId` may get last message id from the compacted topic, while `PersistentTopic#getLastMessageId` don't. ~~And flink-pulsar-connector...
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version master ### Minimal reproduce step The last message id from binary protocal is...
Descriptions of the changes in this PR: Remove the redundant disk read when scannig the entry log file, which could reduce the pressure of disk a lot. ### Motivation We...
### Motivation This is the bug fix simillar to Pulsar. refer to: https://github.com/apache/pulsar/pull/18390. ### Changes Fix bugs in: ``` ConcurrentLongHashMap ConcurrentLongHashSet ConcurrentLongLongHashMap ConcurrentLongLongPairHashMap ConcurrentOpenHashMap ConcurrentOpenHashSet ```
Hi, I have a question about the different Implementation of `ChangeEnsemble` between `BookKeeperProtocol` and `BookKeeperProtocolWithLimbo`. The `ChangeEnsemble` operator in `BookKeeperProtocolWithLimbo` is defined as follows, which only select one faied bookie...
### Motivation In non-transactional production, we update the `LastDataMessagePublishedTimestamp` when the message is persisted successfully. But in transactional production, we do not update `LastDataMessagePublishedTimestamp`, which will impact the feature `ReplicatedSubscription`....