You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Shashikant Banerjee (Jira)" <ji...@apache.org> on 2020/01/16 16:11:00 UTC

[jira] [Created] (RATIS-797) Ratis segment file corruption after server restart

Shashikant Banerjee created RATIS-797:
-----------------------------------------

             Summary: Ratis segment file corruption after server restart
                 Key: RATIS-797
                 URL: https://issues.apache.org/jira/browse/RATIS-797
             Project: Ratis
          Issue Type: Bug
          Components: server
            Reporter: Shashikant Banerjee
            Assignee: Shashikant Banerjee
             Fix For: 0.5.0


While testing ozone, it was observed that ratis segment show corruptions after a server restart
{code:java}
2020-01-08 02:06:46,576 INFO org.apache.ratis.server.raftlog.segmented.LogSegment: Successfully read 1 entries from segment file /metadata/hadoop-ozone/datanode/ratis/data/5e26b460-ca4e-4791-bf70-1fd535056988/current/log_inprogress_0
2020-01-08 02:06:46,576 WARN org.apache.ratis.server.raftlog.segmented.LogSegment: Segment file is corrupted: expected to have 0 entries but only 1 entries read successfully
2020-01-08 02:06:46,580 INFO org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogWorker: 2d422fc8-f7c2-4e41-a59b-abbf76330dfe@group-1FD535056988-SegmentedRaftLogWorker: flushIndex: setUnconditionally 0 -> 0
2020-01-08 02:06:46,618 INFO org.eclipse.jetty.util.log: Logging initialized @1978ms
2020-01-08 02:06:46,738 INFO org.apache.ratis.server.RaftServerConfigKeys: raft.server.snaps

2020-01-16 07:51:12,268 WARN org.apache.ratis.server.raftlog.segmented.LogSegment: Segment file is corrupted: expected to have -3668 entries but only 3500 entries read successfully
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)