You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/17 22:28:00 UTC

[jira] [Commented] (KAFKA-9449) Producer's BufferPool may block the producer from closing.

    [ https://issues.apache.org/jira/browse/KAFKA-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018364#comment-17018364 ] 

ASF GitHub Bot commented on KAFKA-9449:
---------------------------------------

hachikuji commented on pull request #7967: KAFKA-9449: Adds support for closing the producer's BufferPool.
URL: https://github.com/apache/kafka/pull/7967
 
 
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


> Producer's BufferPool may block the producer from closing.
> ----------------------------------------------------------
>
>                 Key: KAFKA-9449
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9449
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Brian Byrne
>            Assignee: Brian Byrne
>            Priority: Major
>
> The producer's BufferPool may block allocations if its memory limit has hit capacity. If the producer is closed, it's possible for the allocation waiters to wait for max.block.ms if progress cannot be made, even when force-closed (immediate), which can cause indefinite blocking if max.block.ms is particularly high.
> The BufferPool should be made close-able, which should immediate wake up any waiters that are pending allocations and throw a "producer is closing" exception.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)