[
https://issues.apache.org/jira/browse/KAFKA-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221881#comment-17221881
]
Jason Gustafson edited comment on KAFKA-10526 at 10/28/20, 1:23 AM:
--------------------------------------------------------------------
[~sagarrao] Yes, of course. I might suggest KAFKA-10652 or KAFKA-10634 as lower
hanging fruits to get into the code a little bit.
was (Author: hachikuji):
[~sagarrao] Yes, of course. I might suggest KAFKA-10652 as a lower hanging
fruit to get into the code a little bit.
> 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)
