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
ConsumerGroupA has topicA, and after few days we move the topicA to ConsumerGroupB due to some use case. Since the retention is infinite for this use cases the ConsumerGroupA for topicA stays active. The lag dashboards keep showing the lag for this dead topic group.
Since other topics are still using ConsumerGroupA we cannot delete the ConsumerGroupA.
We just want to delete the topicA from ConsumerGroupA.
Problems:
The alerts set on the lags result in false alerts due to this. As the alerts come for the dead topic/consumerGroup.
The lag dashboards becomes noisy due to this.
Based on this stackoverflow answer, Kafka 2.4.0+ has support to delete individual consumer group id offsets from a topic which should solve this problem.
Problem Description
Explaining the problem with an example:
ConsumerGroupA
hastopicA
, and after few days we move thetopicA
toConsumerGroupB
due to some use case. Since the retention is infinite for this use cases theConsumerGroupA
for topicA stays active. The lag dashboards keep showing the lag for this dead topic group.Since other topics are still using
ConsumerGroupA
we cannot delete the ConsumerGroupA.We just want to delete the topicA from
ConsumerGroupA
.Problems:
Based on this stackoverflow answer, Kafka 2.4.0+ has support to delete individual consumer group id offsets from a topic which should solve this problem.
KAFKA KIP for --delete-offset
This has a great detail about this problem.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-496%3A+Administrative+API+to+delete+consumer+offsets
Support request
Is it possible to add support for
--delete-offsets
in Sarama?The text was updated successfully, but these errors were encountered: