Lari Hotari

Not directly related to this issue, but related to the use of a large amount of delayed messages: https://github.com/apache/pulsar/discussions/23990#discussioncomment-12233561 It's worth being aware that acknowledgement state could be lost when...

> > Not directly related to this issue, but related to the use of a large amount of delayed messages: [#23990 (reply in thread)](https://github.com/apache/pulsar/discussions/23990#discussioncomment-12233561) It's worth being aware that acknowledgement...

> To prevent this behavior, we reorganized the messages into topics based on their delivery time: • 10 minutes • 1 hour • 1 day • 1 month • infinity...

> ledger zk path is like "/ledgers/00/0601/L7170". But currently it exist pattern regex error cause zk data notification can not execute. Great catch @TakaHiR07. What is the current impact of...

> Some test is requried to ensure the notification logic is triggered and works correct. @thetumbled That's right that there should be tests, but this just shows that the original...

> > Great catch @TakaHiR07. What is the current impact of this in Pulsar & Bookkeeper (which is using PulsarLedgerManager in the Pulsar distribution of Bookkeeper)? > > One impact...

> An extra context switch for each entry is costly, especially when you have many small entries and little or no batching. That's why we put it on the same...

Please check that test image builds are also consistent.

@nodece I remember having some problems with git-commit-id-plugin configuration in the past when someone builds the source code directly without git. Since docker.tag is now set at the top level,...

> @lhotari Both are working fine. > > ``` > # git env > mvn install -pl docker/pulsar,docker/pulsar-all -DskipTests \ > -Pmain,docker,docker-push \ > -Ddocker.platforms=linux/amd64,linux/arm64 \ > -Ddocker.organization=nodece \ >...