[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787274#comment-16787274
]
ASF GitHub Bot commented on KAFKA-8061:
---------------------------------------
hachikuji commented on pull request #6388: KAFKA-8061: Handle concurrent
ProducerId reset and call to Sender thread shutdown
URL: https://github.com/apache/kafka/pull/6388
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
