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

Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/09/25 00:16:00 UTC

[jira] [Created] (KAFKA-10526) Explore performance impact of leader fsync deferral

Jason Gustafson created KAFKA-10526:
---------------------------------------

             Summary: 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


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)