[
https://issues.apache.org/jira/browse/RATIS-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761970#comment-17761970
]
Xinyu Tan edited comment on RATIS-1879 at 9/5/23 6:46 AM:
----------------------------------------------------------
[~szetszwo], it looks like you already addressed the
[issue|https://issues.apache.org/jira/browse/RATIS-677] reported by Ozone four
years ago, which is really cool. Thank you for your thorough work!!!
Now, I would like to continue the discussion based on the last comment in the
[issue|https://issues.apache.org/jira/browse/RATIS-677]. Do we need to consider
changing its default value to WARN_AND_RETURN?
!image-2023-09-05-14-46-35-257.png!
was (Author: tanxinyu):
[~szetszwo], it looks like you already addressed the issue reported by Ozone
four years ago, which is really cool. Thank you for your thorough work!!!
Now, I would like to continue the discussion based on the last comment in the
issue. Do we need to consider changing its default value to WARN_AND_RETURN?
> Handle RaftLog corruption when unsafe flush is enabled.
> -------------------------------------------------------
>
> Key: RATIS-1879
> URL: https://issues.apache.org/jira/browse/RATIS-1879
> Project: Ratis
> Issue Type: Bug
> Components: server
> Affects Versions: 3.0.0, 2.5.1
> Reporter: Song Ziyang
> Assignee: Tsz-wo Sze
> Priority: Major
> Attachments: image-2023-09-05-14-46-35-257.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During normal operations of the RaftServer, its containing virtual machine
> (VM) was unexpectedly shut down and subsequently restarted. Following the VM
> reboot, *our attempts to restart the RaftServer led to encountering the
> subsequent exception, indicating corruption in the Raft* {*}Log{*}{*}.{*}
> *The details of this exception please refer to
> [https://apache-iotdb.feishu.cn/docx/Zmyudq0FYoDVcsxDwHpcINyznfg]*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
