Jyotirmoy Sinha created HDDS-12753:
--------------------------------------

             Summary: OM down due to IllegalStateException - initRaftLog
                 Key: HDDS-12753
                 URL: https://issues.apache.org/jira/browse/HDDS-12753
             Project: Apache Ozone
          Issue Type: Bug
          Components: OM
            Reporter: Jyotirmoy Sinha
            Assignee: Sadanand Shenoy


OM Error stacktrace -
{code:java}
2025-03-25 05:53:55,389 INFO 
[om122-impl-thread1]-org.apache.ratis.server.raftlog.segmented.LogSegment: 
Successfully read 2137 entries from segment file 
/var/lib/hadoop-ozone/om/ratis/ba1cddf6-44cb-315f-9e8b-422d5043f17e/current/log_471502685-471504821
2025-03-25 05:53:55,393 ERROR 
[main]-org.apache.hadoop.ozone.om.OzoneManagerStarter: OM start failed with 
exception
java.util.concurrent.CompletionException: java.lang.IllegalStateException: 
om122@group-422D5043F17E: Failed to initRaftLog.
        at 
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
        at 
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
        at 
java.util.concurrent.CompletableFuture.biRelay(CompletableFuture.java:1298)
        at 
java.util.concurrent.CompletableFuture$BiRelay.tryFire(CompletableFuture.java:1284)
        at 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
        at 
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1990)
        at 
org.apache.ratis.util.ConcurrentUtils.accept(ConcurrentUtils.java:191)
        at 
org.apache.ratis.util.ConcurrentUtils.lambda$null$4(ConcurrentUtils.java:180)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: om122@group-422D5043F17E: Failed to 
initRaftLog.
        at 
org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:222)
        at 
org.apache.ratis.server.impl.ServerState.lambda$new$5(ServerState.java:161)
        at org.apache.ratis.util.MemoizedSupplier.get(MemoizedSupplier.java:62)
        at 
org.apache.ratis.server.impl.ServerState.initialize(ServerState.java:177)
        at 
org.apache.ratis.server.impl.RaftServerImpl.start(RaftServerImpl.java:338)
        at 
org.apache.ratis.util.ConcurrentUtils.accept(ConcurrentUtils.java:188)
        ... 4 more
Caused by: org.apache.ratis.protocol.exceptions.ChecksumException: Log entry 
corrupted: Calculated checksum is FC6801F0 but read checksum is 00000000.
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogReader.decodeEntry(SegmentedRaftLogReader.java:321)
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogReader.readEntry(SegmentedRaftLogReader.java:203)
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogInputStream.nextEntry(SegmentedRaftLogInputStream.java:131)
        at 
org.apache.ratis.server.raftlog.segmented.LogSegment.readSegmentFile(LogSegment.java:131)
        at 
org.apache.ratis.server.raftlog.segmented.LogSegment.loadSegment(LogSegment.java:164)
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLogCache.loadSegment(SegmentedRaftLogCache.java:381)
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.loadLogSegments(SegmentedRaftLog.java:241)
        at 
org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.openImpl(SegmentedRaftLog.java:214)
        at 
org.apache.ratis.server.raftlog.RaftLogBase.open(RaftLogBase.java:251)
        at 
org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:239)
        at 
org.apache.ratis.server.impl.ServerState.initRaftLog(ServerState.java:220)
        ... 9 more{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to