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

Posted to jira@kafka.apache.org by "Sagar Rao (Jira)" <ji...@apache.org> on 2020/12/05 16:33:00 UTC

[jira] [Commented] (KAFKA-10652) Raft leader should flush accumulated writes after a min size is reached

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

Sagar Rao commented on KAFKA-10652:
-----------------------------------

hey [~hachikuji], sorry for being nosey here but did you get a chance to review the approach here.. 

> Raft leader should flush accumulated writes after a min size is reached
> -----------------------------------------------------------------------
>
>                 Key: KAFKA-10652
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10652
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: Sagar Rao
>            Priority: Major
>
> In KAFKA-10601, we implemented linger semantics similar to the producer to let the leader accumulate a batch of writes before fsyncing them to disk. Currently the fsync is only based on the linger time, but it would be helpful to make it size-based as well. In other words, if we accumulate a configurable N bytes, then we should not wait for linger expiration and should just fsync immediately.



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