You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps I'm missing the way to check for such an error, but I cant seem to cause a failure when creating two client, in the same consumer group, with the same instance ID.
According to the Kafka spec we should be getting a FencedInstanceID error, as defined in kerr. (KIP-345)
I have run this against Kafka 2.5.1 and can confirm that the broker logs do in fact mentioned returning this error
[2023-06-24 15:09:33,711] ERROR given member.id myistance-dac57156-ae34-4b3c-8f90-98d6f4b0aa6d is identified as a known static member myistance, but not matching the expected member.id myistance-02a09bac-1a4a-453d-b5f9-6e124ea65b77 during join-group, will respond with instance fenced error (kafka.coordinator.group.GroupMetadata)
The way I tested it was simply creating two client like so:
Poll previously would not return if only a fake fetch existed. For
example, if a user joined a group with an instance ID twice, the fenced
group member would never exit polling. We now check both the actual
ready sources and the fake sources in our poll condition loop.
Closes#479.
Hi,
Perhaps I'm missing the way to check for such an error, but I cant seem to cause a failure when creating two client, in the same consumer group, with the same instance ID.
According to the Kafka spec we should be getting a FencedInstanceID error, as defined in
kerr
. (KIP-345)I have run this against Kafka 2.5.1 and can confirm that the broker logs do in fact mentioned returning this error
The way I tested it was simply creating two client like so:
When trying with confluent kafka go I seem to get an error, although it appears to be in the form of a
panic
admittedly..Any assistance is much appreciated.
The text was updated successfully, but these errors were encountered: