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

Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2019/03/07 23:39:00 UTC

[jira] [Resolved] (KAFKA-8061) Handle concurrent ProducerId reset and call to Sender thread shutdown

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

Jason Gustafson resolved KAFKA-8061.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.1
                   2.1.2
                   2.0.2

> Handle concurrent ProducerId reset and call to Sender thread shutdown
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-8061
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8061
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Manikumar
>            Assignee: Manikumar
>            Priority: Major
>             Fix For: 2.0.2, 2.1.2, 2.2.1
>
>
> In KAFKA-5503, we have added a check (https://github.com/apache/kafka/pull/5881) for `running` flag in the loop inside maybeWaitForProducerId.  This is to handle concurrent call to Sender close(), while we attempt to get the ProducerId.
> This avoids blocking indefinitely when the producer is shutting down.
> This created a corner case, where Sender thread gets blocked, if we had concurrent producerId reset and call to Sender thread close. The proposed fix is to check the forceClose flag in the loop inside maybeWaitForProducerId.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)