Lari Hotari

You can achieve this by setting this config: ```yaml bookkeeper: configData: # this configures journalWriteData=false in /pulsar/conf/bookkeeper.conf PULSAR_PREFIX_journalWriteData: "false" ``` journalWriteData is documented [in the default config file](https://github.com/apache/bookkeeper/blob/7c9c42960ad85760fbf0a3d6b30f9faceb16948a/conf/bk_server.conf#L354-L360) of Bookkeeper....

@danielnaumau Would you like to contribute improvements to the README to document how to configure specific configuration options?

There is a workaround. Excluding works if you have all patterns in the same "level", for example ``` path: | ~/.m2/repository/*/*/* !~/.m2/repository/org/apache/pulsar ``` this is what we use in apache/pulsar,...

Bumping this issue. We ran into this problem In Pulsar's dev mailing list recently and were wondering what was causing the behavior. https://lists.apache.org/thread/jc7nbbpxr10g69wwkoz3h1yxyjd9ncpd

Flaky-test: org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer Number of failures: 11 org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest is flaky. The testAddRemoveConsumer test method fails sporadically. ``` java.lang.AssertionError: expected object to not be null at org.testng.Assert.fail(Assert.java:110) at org.testng.Assert.assertNotNull(Assert.java:1483) at org.testng.Assert.assertNotNull(Assert.java:1467) at...

Recent failure: Flaky-test: org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer Number of failures: 1 org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest is flaky. The testAddRemoveConsumer test method fails sporadically. ``` java.lang.AssertionError: expected object to not be null at org.testng.Assert.fail(Assert.java:110) at org.testng.Assert.assertNotNull(Assert.java:1483) at...

Flaky-test: org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer Number of failures: 5 org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest is flaky. The testAddRemoveConsumer test method fails sporadically. ``` java.lang.AssertionError: expected object to not be null at org.testng.Assert.fail(Assert.java:110) at org.testng.Assert.assertNotNull(Assert.java:1483) at org.testng.Assert.assertNotNull(Assert.java:1467) at...

It seems that PIP-282 added some subscription stats in https://github.com/apache/pulsar/pull/21953 that improve observability of Key_Shared.

There's already a counter for message redelivery: https://github.com/apache/pulsar/blob/77b6378ae8b9ac83962f71063ad44d6ac57f8e32/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/Consumer.java#L959-L961 However, this isn't currently exposed in the subscription stats. This counter was added as part of Otel changes in https://github.com/apache/pulsar/pull/22693 . There's...

[PIP-379: Key_Shared Draining Hashes for Improved Message Ordering](https://github.com/apache/pulsar/blob/master/pip/pip-379.md) covers observability.