k32
k32
Hi @gabrielemontano , it looks like you're using a wrong base for your PR. Currently there are two trunks in this repo: - master (for EMQ X 5.0) - main-4.3...
Hi, > I figured one solution (as of 4.3.10) is to use address_type = hostname, and mnesia will always read from a consistent directory (since the $NODE_NAME is consistent). But...
Hi! > How many is too many? It depends on the broker settings. We don't use Confluent-managed Kafka, so I don't know how many parallel connections per host they allow....
Hi! Sorry for silence. We are aware of this problem (or rather two separate problems), but we haven't got any good solutions yet, other than client restart workaround. It's definitely...
Hi! First of all, a disclaimer: `group_subscriber_v2` behavior is currently experimental, there are some known issues with it that I, unfortunately, didn't have time to fix. In particular, it may...
Hi! Sorry for the long delay in responses. I think I identified the problem. It's likely related to how `brod_topic_subscriber` works internally. It tries to reuse a consumer, which is...
Yes, definitely switch to v1 for now, if you're doing anything serious. edit: P.S. Old behavior doesn't use topic_subscriber under the hood, hence it doesn't demonstrate this bug.
Please keep the issue open, I will use it as a reference for the fix.
Hmm, turns out I was mistaken and v1 subscriber might be also affected by this issue.
Sorry, it took me a while to fix it, mostly due to test suite deficiencies.