[
https://issues.apache.org/jira/browse/KAFKA-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215353#comment-17215353
]
Sagar Rao edited comment on KAFKA-10526 at 10/16/20, 11:36 AM:
---------------------------------------------------------------
hey [~hachikuji], is it something that I can pick up? I am not sure if you or
someone else is planning to pick it as it seems to be related to the raft
protocol KIP and might be of higher priority.. Let me know plz..
was (Author: sagarrao):
hey [~hachikuji], is it something that I can pick up? I am not sure if you or
someone else is planning to pick it as it seems to be related to the raft
protocol KIP.. Let me know plz.
> Explore performance impact of leader fsync deferral
> ---------------------------------------------------
>
> Key: KAFKA-10526
> URL: https://issues.apache.org/jira/browse/KAFKA-10526
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jason Gustafson
> Priority: Major
>
> In order to commit a write, a majority of nodes must call fsync in order to
> ensure the data has been written to disk. An interesting optimization option
> to consider is letting the leader defer fsync until the high watermark is
> ready to be advanced. This potentially allows us to reduce the number of
> flushes on the leader.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
