[
https://issues.apache.org/jira/browse/RATIS-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764829#comment-17764829
]
Tsz-wo Sze commented on RATIS-1886:
-----------------------------------
[~weichiu], thanks a lot for testing it in Ozone. Could you also try 0ms? If
there are not much difference between 1ms and 0ms, we should set it to 1ms to
avoid too frequent appendEntires calls in the error cases.
> AppendLog sleep fixed time cause significant drop in write throughput
> ---------------------------------------------------------------------
>
> Key: RATIS-1886
> URL: https://issues.apache.org/jira/browse/RATIS-1886
> Project: Ratis
> Issue Type: Improvement
> Components: server
> Affects Versions: 2.5.1
> Reporter: Yaolong Liu
> Priority: Major
> Attachments: image-2023-09-13-15-44-00-933.png
>
>
> In https://issues.apache.org/jira/browse/RATIS-1793 , we enforce
> raft.server.log.appender.wait-time.min, which make GrpcLogAppender sleep
> fixed time during appendLog. This make alluxio master write throughput drop
> 50% and unacceptable. The ops of alluxio master could see below
> !image-2023-09-13-15-44-00-933.png!
> I noticed that this patch was introduced to avoid leader being too busy in
> some error conditions. Could we introduce sleep waiting when an error is
> discovered (maybe not easy) or find a way to locate the error condition and
> repair it completely? The performance degradation caused by sleeping for each
> appendLog request may be underestimated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)