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 2017/10/29 09:33:00 UTC

[jira] [Resolved] (KAFKA-601) ConsumerConnector.shutdown() hangs if autocommit is enabled, and no zk available

     [ https://issues.apache.org/jira/browse/KAFKA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar resolved KAFKA-601.
-----------------------------
    Resolution: Auto Closed

Closing inactive issue. The old consumer is no longer supported.

> ConsumerConnector.shutdown() hangs if autocommit is enabled, and no zk available
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-601
>                 URL: https://issues.apache.org/jira/browse/KAFKA-601
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.7.2
>            Reporter: Jason Rosenberg
>
> Hi,
> I have a situation where I want to reliably shut-down a consumer, but it seems to hang in certain conditions, namely:
> - If autocommit.enabled = true
> - If the current zk instance is not available
> It seems that it will indefinitely try to re-create the zk connection, in order to auto-commit, before exiting, even after I've called ConsumerConnector.shutdown().
> I would think that there should be a way to force it to shutdown, even under error conditions.
> Jason



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)