You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2016/04/11 22:48:25 UTC

[jira] [Updated] (KAFKA-3540) KafkaConsumer.close() may block indefinitely

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

Oleg Zhurakousky updated KAFKA-3540:
------------------------------------
    Description: 
KafkaConsumer API doc states 
{code}
Close the consumer, waiting indefinitely for any needed cleanup. . . . 
{code}

That is not acceptable as it creates an artificial deadlock which directly affects systems that rely on Kafka API essentially rendering them unavailable.

Consider adding _close(timeout)_ method

  was:
KafkaConsumer API doc states 
{code}
Close the consumer, waiting indefinitely for any needed cleanup. . . . 
{code}

That is not acceptable as it creates an artificial deadlock which directly affects systems that rely on Kafka API essentially rendering them unavailable.


> KafkaConsumer.close() may block indefinitely
> --------------------------------------------
>
>                 Key: KAFKA-3540
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3540
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Oleg Zhurakousky
>
> KafkaConsumer API doc states 
> {code}
> Close the consumer, waiting indefinitely for any needed cleanup. . . . 
> {code}
> That is not acceptable as it creates an artificial deadlock which directly affects systems that rely on Kafka API essentially rendering them unavailable.
> Consider adding _close(timeout)_ method



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)