Hi Ka, Since there is a ReferenceCountedLeakDetector in the log, I guess you were using the master branch? The problem looks like a Zero-copy bug in the master branch. Currently, the Zero-copy feature is incomplete. Both Ratis 3.1.0 and the upcoming Ratis 3.1.1 do not contain the zero-copy feature.
Tsz-Wo On Fri, Sep 13, 2024 at 8:03 AM ka yuu <[email protected]> wrote: > *HI, Ratis community, I encountered this problem: * 2024-09-10 > 21:22:59,080 [0@group-000000000000-StateMachineUpdater] ERROR > o.a.r.s.i.StateMachineUpdater:206 - 0@group-000000000000-StateMachineUpdater > caught a Throwable. java.lang.IllegalStateException: Failed to retain: > object has already been completely released. at > org.apache.ratis.util.ReferenceCountedLeakDetector$Impl.retain(ReferenceCountedLeakDetector.java:121) > at > org.apache.ratis.server.raftlog.segmented.SegmentedRaftLog.retainLog(SegmentedRaftLog.java:310) > at > org.apache.ratis.server.impl.StateMachineUpdater.applyLog(StateMachineUpdater.java:244) > at > org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:193) > at java.base/java.lang.Thread.run(Thread.java:834) 2024-09-10 21:22:59,081 > [0@group-000000000000-StateMachineUpdater] INFO > o.a.r.s.i.RaftServerImpl:513 - 0@group-000000000000: shutdown 2024-09-10 > 21:22:59,081 [0@group-000000000000-StateMachineUpdater] INFO > o.a.r.util.JmxRegister:74 - Successfully un-registered JMX Bean with object > name Ratis:service=RaftServer,group=group-000000000000,id=0 > > *Is this resolved in 3.1.1?* >
