Lari Hotari
Lari Hotari
> Before [48ffb7a](https://github.com/apache/pulsar/commit/48ffb7abfe1b5d5ad71cc3a07627326fb84c7a5a), there is a constructor parameter that determines whether to initialize the `NamespaceName`. I also compared with the existing `TopicName` constructor, which can be found here: https://gist.github.com/BewareMyPower/6b83c897552c110f336e51965cc91c24 >...
@BewareMyPower My point from an earlier comment isn't addressed: > If we'd completely remove the cache, there would be more duplicate TopicName and NamespaceName instances and more duplicate string instance....
This PR will be an improvement. Regarding the argument I made in a previous comment about duplicate tenant and namespace `java.lang.String` instances, that problem is already present in the current...
> @codelipenghui @lhotari @coderzc @Apurva007 > How does this copy on write method look, is my direction correct? > There is still much work to be done, and I will...
There's been references to https://github.com/apache/pulsar/pull/6326 and https://github.com/apache/pulsar-client-go/issues/1395 which explain the context. Similar logic as https://github.com/apache/pulsar/pull/6326/files#diff-d6fcf8aa2d0035cc386dca0942a452343d6854763c7fd397efa4e660c0069767 would be needed.
> Without studying it closely, I see a lot of mentioning of batching. I just want to make sure this is not a "Producer sending batches" issue, since DotPulsar only...
2 other threads related to the dead lock, in `TableViewLoadDataStoreImpl.removeAsync` method: > [pulsar-load-manager-6391-1](https://jstack.review/?https://gist.github.com/lhotari/17557838cea2e4d4f4f1556fd4caec98#tda_1_threaddetails_0x00007f4fd8e276e0)waiting to acquire [ [0x000010002025ce08](https://jstack.review/?https://gist.github.com/lhotari/17557838cea2e4d4f4f1556fd4caec98#tda_1_sync_0x000010002025ce08) ] , holding [ [0x000010001e5511f0](https://jstack.review/?https://gist.github.com/lhotari/17557838cea2e4d4f4f1556fd4caec98#tda_1_sync_0x000010001e5511f0) [0x00001000202630c0](https://jstack.review/?https://gist.github.com/lhotari/17557838cea2e4d4f4f1556fd4caec98#tda_1_sync_0x00001000202630c0) ] > at org.apache.pulsar.broker.loadbalance.extensions.store.TableViewLoadDataStoreImpl.removeAsync(TableViewLoadDataStoreImpl.java) > at org.apache.pulsar.broker.loadbalance.extensions.channel.ServiceUnitStateChannelImpl.doCleanup(ServiceUnitStateChannelImpl.java:1602)...
TableViewLoadDataStoreImpl.removeAsync was made synchronized in #21777
More recent issue: https://jstack.review/?https://gist.githubusercontent.com/lhotari/a09177d45f1b8589c44fd3b4b4f42c82/raw/cd34a52e0f49cc7672e6cba1867f171bb8f5da64/threaddump4268_2025-11-11_00.txt#tda_1_dump full logs: https://gist.github.com/lhotari/a09177d45f1b8589c44fd3b4b4f42c82
> the changes to `maxMessagePublishBufferSizeInMB` and `managedLedgerCacheSizeMB` should be highlighted strongly in the release notes. They can even be considered as breaking changes. Most of the production systems might be...