Xushaohong opened a new pull request #2840:
URL: https://github.com/apache/ozone/pull/2840
## What changes were proposed in this pull request?
If the IO exception is met during the raft log being written for the leader
SCM, it will endlessly be stuck in the timeout exception.
We should let the leader SCM crash for this kind of IO issue and possibly
this will **notice the maintainer**.
After the SCM crashes, there are two scenarios:
1. IO-err SCM restarted:
Most likely, it will become a follower and even it cannot commit a raft
log, it won't affect the leader.
2. IO-err SCM not restarted:
There are two SCMs remain working, which is still doable for ratis.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5976
## How was this patch tested?
manual test in K8S
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
