Hi Tsz-wo, Thanks for confirming this! Hoping this fix can catch 2.4.0 release.
BTW, I see that the community has closed Release 2.4.0-rc1 voting process due to compatibility issues. What is the current progress? Our community (IoTDB) plans to release a major version 0.14.0, which relies on features that will introduced in 2.4.0. Please let me know if there’s anything we can help. Regards, William > 2022年9月8日 08:31，Tsz Wo Sze <[email protected]> 写道： > > Hi William, > > Thanks a lot for reporting the problem! Fortunately, the race > condition happens during shutdown since "SegmentRaftLog is closed" as > mentioned in the description of RATIS-1699. Of course, we would like > to fix it. I will check it for more details. > > Tsz-Wo > > On Wed, Sep 7, 2022 at 11:39 PM William Song <[email protected]> wrote: >> >> Hi, >> >> We found abnormal behaviors of GrpcLogAppender in a recent run, please refer >> to https://issues.apache.org/jira/browse/RATIS-1699 >> <https://issues.apache.org/jira/browse/RATIS-1699> for detailed error log >> and problem description. >> >> We think that this problem roots in the data race in LeaderStateImpl. Its >> method stop() and restart(LogAppender) can be called concurrently, and under >> certain event sequence, will cause this weird situation. Maybe we can add >> synchronizations to coordinate these two methods. The event sequence and >> full logs are also provided in this issue. >> >> Please help me to confirm whether our analysis stands. Thanks in advance! >> >> Regards, >> William
