You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/06/15 18:50:00 UTC
[jira] [Resolved] (KAFKA-4723) offsets.storage=kafka - groups stuck
in rebalancing with committed offsets
[ https://issues.apache.org/jira/browse/KAFKA-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manikumar resolved KAFKA-4723.
------------------------------
Resolution: Auto Closed
Closing inactive issue. The old consumer is no longer supported. Please upgrade to the Java consumer whenever possible.
> offsets.storage=kafka - groups stuck in rebalancing with committed offsets
> --------------------------------------------------------------------------
>
> Key: KAFKA-4723
> URL: https://issues.apache.org/jira/browse/KAFKA-4723
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.1
> Reporter: biker73
> Priority: Minor
>
> Hi, I have moved offset store to kafka only, when I now run;
> bin/kafka-consumer-groups.sh --bootstrap-server localhost:9094 --describe --new-consumer --group my_consumer_group
> I get the message;
> Consumer group `my_consumer_group` does not exist or is rebalancing.
> I have found the issue KAFKA-3144 however this refers to consumer groups that have no committed offsets, the groups I am looking do and are constantly in use.
> using --list I get all my consumer groups returned. Although some are inactive I have around 6 very active ones (millions of messages a day constantly). looking at the mbean data and kafka tool etc I can see the lags and offsets changing every second. Therefore I would expect the kafka-consumer-groups.sh script to return the lags and offsets for all 6 active consumer groups.
> I think what has happened is when I moved offset storage to kafka from zookeeper (and then disabled sending to both), something has got confused. Querying zookeeper I get the offsets for the alleged missing consumer groups - but they should be stored and committed to kafka.
> Many thanks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)