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 2021/01/11 15:27:00 UTC

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

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

Sagar Rao commented on KAFKA-10526:
-----------------------------------

[~hachikuji], while KAFKA-10652  is getting reviewed, I was wondering if I can get started on this one. Any pointers/docs on how to perform the benchmarking? I will also start looking at the points where fsync deferral can be made post the crossing of high watermark.

> 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
>            Assignee: Sagar Rao
>            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)