[
https://issues.apache.org/jira/browse/KAFKA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huxi updated KAFKA-4295:
------------------------
Comment: was deleted
(was: I think we'd better follow what 0.8.x does for us. Removed consumer
group's persisitent nodes after it became inactive in case of polluting
zookeeper, if we did not specify "group.id" for the console consumer.)
> kafka-console-consumer.sh does not delete the temporary group in zookeeper
> --------------------------------------------------------------------------
>
> Key: KAFKA-4295
> URL: https://issues.apache.org/jira/browse/KAFKA-4295
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.9.0.1, 0.10.0.0, 0.10.0.1
> Reporter: Sswater Shi
> Assignee: huxi
> Priority: Minor
>
> I'm not sure it is a bug or you guys designed it.
> Since 0.9.x.x, the kafka-console-consumer.sh will not delete the group
> information in zookeeper/consumers on exit when without "--new-consumer".
> There will be a lot of abandoned zookeeper/consumers/console-consumer-xxx if
> kafka-console-consumer.sh runs a lot of times.
> When 0.8.x.x, the kafka-console-consumer.sh can be followed by an argument
> "group". If not specified, the kafka-console-consumer.sh will create a
> temporary group name like 'console-consumer-xxxx'. If the group name is
> specified by "group", the information in the zookeeper/consumers will be kept
> on exit. If the group name is a temporary one, the information in the
> zookeeper will be deleted when kafka-console-consumer.sh is quitted by
> Ctrl+C. Why this is changed from 0.9.x.x.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
