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
We recently had to adjust the offsets of a partition in Azure EventHub. However, it didn't work:
When resetting the offsets while a consumer was active, kafkactl refused to do so. This is expected:
❯ kafkactl reset consumer-group-offset some-consumer-group --topic some-topic --partition 10 --offset 847082914 --execute
cannot reset offsets on consumer group some-consumer-group. There are consumers assigned (state: Stable)
However, after stopping the consumer, resetting the offset was still not possible;:
❯ kafkactl reset consumer-group-offset some-consumer-group --topic some-topic --partition 10 --offset 847082914 --execute
cannot reset offsets on consumer group some-consumer-group. There are consumers assigned (state: Dead)
Looking at the code, setting offsets is only allowed when the consumer group is in state Empty. However, it seems like the Azure EventHub Kafka interface skips the Empty state and goes directly to Dead once no consumer is present on the group. At least that's the observation. I wasn't able to find documentation from Microsoft regarding this behavior.
Using a locally built kafkactl version with the check patched out, resetting the offsets worked even with the consumer group being in the Dead state. Looking at the Kafka command line tool, it also allows resetting the offsets when a group is in the Dead state.
If wanted, I can try to create a PR.
The text was updated successfully, but these errors were encountered:
We recently had to adjust the offsets of a partition in Azure EventHub. However, it didn't work:
When resetting the offsets while a consumer was active, kafkactl refused to do so. This is expected:
However, after stopping the consumer, resetting the offset was still not possible;:
Looking at the code, setting offsets is only allowed when the consumer group is in state
Empty
. However, it seems like the Azure EventHub Kafka interface skips theEmpty
state and goes directly toDead
once no consumer is present on the group. At least that's the observation. I wasn't able to find documentation from Microsoft regarding this behavior.Using a locally built kafkactl version with the check patched out, resetting the offsets worked even with the consumer group being in the
Dead
state. Looking at the Kafka command line tool, it also allows resetting the offsets when a group is in theDead
state.If wanted, I can try to create a PR.
The text was updated successfully, but these errors were encountered: