kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4160) Consumer onPartitionsRevoked should not be invoked while holding the coordinator lock
Date Thu, 15 Sep 2016 05:32:20 GMT

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

Guozhang Wang resolved KAFKA-4160.
----------------------------------
    Resolution: Fixed

Issue resolved by pull request 1855
[https://github.com/apache/kafka/pull/1855]

> Consumer onPartitionsRevoked should not be invoked while holding the coordinator lock
> -------------------------------------------------------------------------------------
>
>                 Key: KAFKA-4160
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4160
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Blocker
>             Fix For: 0.10.1.0
>
>
> We have a single lock which is used for protecting access to shared coordinator state
between the foreground thread and the background heartbeat thread. Currently, the onPartitionsRevoked
callback is invoked while holding this lock, which prevents the heartbeat thread from sending
any heartbeats. If the heartbeat thread is blocked for longer than the session timeout, than
the consumer is kicked out of the group. Typically this is not a problem because onPartitionsRevoked
might only commit offsets, but for Kafka Streams, there is some expensive cleanup logic which
can take longer than the session timeout.



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

Mime
View raw message