Michał Cukierman

For the framework using (extending) SmallRye Reactive Messaging we've used: https://github.com/weld/weld-testing/tree/master/junit5

We had a similar issue, it turns out that `broker-init` and `pulsar-init` scripts run on an image that need at least 2.5Mi of memory. If the job is run on...

It still happens even after setting: ``` resources: requests: memory: 3Gi limits: memory: 3Gi ```

I think the same issue will appear on shared subscription, where cumulative ack cannot be used, no?

We have faced the same issue in Pulsar 3.1.3 and Java Client 3.2.1. There was a race condition, consumers/producers were created during setting on a namespace level: ``` allowAutoTopicCreation: true...

Two files attached: [partitioned.stats.internal.txt](https://github.com/apache/pulsar/files/12497246/partitioned.stats.internal.txt) [partitioned.stats.txt](https://github.com/apache/pulsar/files/12497248/partitioned.stats.txt) I see that in stats we have: ``` "availablePermits" : 0, "unackedMessages" : 25, "availablePermits" : 0, "unackedMessages" : 32, ``` , but I do...

Here are the alternative stats: https://github.com/apache/pulsar/issues/21082#issuecomment-1698836870

I think it happens: - there is ackTimeout set on a consumer - high throughput - the receviverQueue size is low There may be a race condition in 3.1.0 client,...

It's 1 mln x 30 kb of sample HTML file. Any text file would be good. What we are doing: `topic:source ( 1mln x 30k)` -> ` app:router` -> `topic:destination`...

Here is the exact payload: [30k.html.zip](https://github.com/apache/pulsar/files/12526279/30k.html.zip)