[
https://issues.apache.org/jira/browse/KAFKA-13884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17542183#comment-17542183
]
Jose Armando Garcia Sancio commented on KAFKA-13884:
----------------------------------------------------
> The second solution is I can refer/ refactor the PR :
> https://issues.apache.org/jira/browse/KAFKA-10652.
That Jira is talking about the batching/buffering that the leader does when
constructing a record batch. I think the solution for that Jira is different
from the solution to this Jira.
> KRaft Obsever are not required to flush on every append
> -------------------------------------------------------
>
> Key: KAFKA-13884
> URL: https://issues.apache.org/jira/browse/KAFKA-13884
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jose Armando Garcia Sancio
> Priority: Major
>
> The current implementation of the KRaft Client flushes to disk when observers
> append to the log. This is not required since observer don't participate in
> leader election and the advancement of the high-watermark.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
