Yunze Xu
> Is there any guarantee that when a consumer becomes active for a topic, it always receives a CommandActiveConsumerChange before the first message? Yes, you can see the following code...
What's your client and producer configs? There was a similar issue happened when `maxReconnectAttempts` is 1: https://github.com/apache/pulsar-client-go/issues/1312#issuecomment-2597791188
It seems that you're using Python clients. What's the client version? Could it be reproduced with the latest Python client (3.6.1)?
Could it be reproduce it via a simple C++ application? What's the C++ client version you're using? The pre-built binaries or you built from source? It's recommended to use vcpkg...
I cannot reproduce this issue with the code above against a standalone. - client: 3be5267ef781b9a1928c009da1ac53dc60a12a35 - broker: 4.1.1 @nodece If you can reproduce, could you share the full logs?
Ah, that's right, it can be reproduced by 3.7.2 client on macOS. But this issue should have been fixed in master branch. Not sure which PR fixes it for now.
Interesting, it can be reproduce on master branch as well, let me take a look
BTW, you can leverage AI tool (e.g. Copilot) to improve the documents with more professional expression.
> The reason for this is that in many cases there's a clear reason why then*Async has been used. +1. Generally, `thenXxxAsync` has poor performance due to the thread switching....