[
https://issues.apache.org/jira/browse/RATIS-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763198#comment-17763198
]
Tsz-wo Sze commented on RATIS-1763:
-----------------------------------
[~Nicholas Niu], this looks like a different issue. Could you file a JIRA?
bq. 1. shutdown scm, shutdown more than 60s timeout kill -9
It looks like that the log was partially written due to "kill -9". Could you
try setting raft.server.log.corruption.policy to WARN_AND_RETURN?
> Gap between logs caused by purging order
> ----------------------------------------
>
> Key: RATIS-1763
> URL: https://issues.apache.org/jira/browse/RATIS-1763
> Project: Ratis
> Issue Type: Bug
> Components: server
> Affects Versions: 2.4.1
> Reporter: Song Ziyang
> Assignee: Song Ziyang
> Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Attachments: image-2023-09-08-10-18-36-198.png,
> ozone-work-scm-test17-before-restart.log, ozone-work-scm-test17.log
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> java.lang.IllegalStateException Found a gap between logs: the last log
> segment log-88826_88927 ended at 88927 but the next log segment
> log-89130_89071 started at 89130.
> It is caused by log purging order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
