[
https://issues.apache.org/jira/browse/RATIS-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796254#comment-17796254
]
Song Ziyang edited comment on RATIS-1966 at 12/13/23 12:37 PM:
---------------------------------------------------------------
??I guess you also saw the following log many times???
It's weird that I don't find any logs indicating leader restarting. According
to the code, the leader won't restart if it is just unable to contact a
follower.
??Yes. If we can detect the log message being the same .... We may add a log
message id for particular messages and record the last printed time.??
Good idea! let me implement it.
was (Author: JIRAUSER281912):
> I guess you also saw the following log many times?
It's weird that I don't find any logs indicating leader restarting. According
to the code, the leader won't restart if it is just unable to contact a
follower.
> Yes. If we can detect the log message being the same .... We may add a log
> message id for particular messages and record the last printed time.
Good idea! let me implement it.
> Warning logs flooding when a peer is down
> -----------------------------------------
>
> Key: RATIS-1966
> URL: https://issues.apache.org/jira/browse/RATIS-1966
> Project: Ratis
> Issue Type: Improvement
> Components: gRPC
> Affects Versions: 3.0.0
> Reporter: Song Ziyang
> Assignee: Song Ziyang
> Priority: Minor
> Attachments: image-2023-12-12-11-02-46-776.png,
> image-2023-12-12-11-14-02-145.png
>
>
> Warnings like
> 2023-12-12 10:58:01,764 [grpc-default-executor-6] WARN
> o.a.ratis.util.LogUtils:121 -
> 2@group-000100000010->3-AppendLogResponseHandler: Failed appendEntries:
> org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
> exception
> are flooding when there is a follower currently down.
> thousands of logs are printed in several tens of seconds.
> !image-2023-12-12-11-14-02-145.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
