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

Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/12/09 21:35:00 UTC

[jira] [Resolved] (KAFKA-10826) Ensure raft io thread wakes up after linger expiration

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

Jason Gustafson resolved KAFKA-10826.
-------------------------------------
    Resolution: Fixed

> Ensure raft io thread wakes up after linger expiration
> ------------------------------------------------------
>
>                 Key: KAFKA-10826
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10826
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> When scheduling an append, we currently only wakeup the IO thread after the batch is ready to drain. If the IO thread is blocking in `poll()`, there is no guarantee that it will get woken up by a subsequent append. We need to ensure that the thread gets woken up at least once when the linger timer starts ticking so that the IO thread will be ready when the batch is ready to drain.



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