Duong, thanks a lot for starting the 3.1.1 discussion. Xinyu, agree, we should include RATIS-2138 and RATIS-2136
The following are the outstanding issues: 1. RATIS-2132: need a fix or revert RATIS-2099 2. RATIS-2141: revert RATIS-1983 from 3.1.0 (the master branch is already fixed) 3. RATIS-2144: need a simple fix. I will go through the commits after. To see if there are other issues which should be included. Tsz-Wo On Tue, Aug 20, 2024 at 11:34 PM Xinyu Tan <[email protected]> wrote: > Hi, Duong > > We IoTDB team have fixed RATIS-2138 Remove uncessary error log in > JVMPauseMonitor When GC is serious and RATIS-2136 Fixed the issue that > RatisServer could not start after frequent restarts after Ratis 3.1.0. > > These two issues are straightforward to reproduce and easy to fix, and may > also be encountered in the Ozone. > > We hope these two issues will be included in 3.1.1 as well. > > Best > ------------------- > Xinyu Tan > Apache IoTDB PMC > > Duong Nguyen <[email protected]> 于2024年8月21日周三 09:14写道： > > > Hi Ratis community, > > > > I would like to start the discussion to release Ratis 3.1.1. While > working > > on adopting ratis 3.1.0 in Apache Ozone, we found a couple of blocking > > issues with this release: > > 1. RATIS-2132 <https://issues.apache.org/jira/browse/RATIS-2132>: > > performance regression from RATIS-2099. > > 2. RATIS-2141 <https://issues.apache.org/jira/browse/RATIS-2141>: Memory > > leak for stateMachineCache use cases > > > > The second is a critical issue that prevents Ozone from being released > with > > Ratis 3.1.0. I want to check if we can quickly roll out a Ratis 3.1.1 (on > > top of 3.1.0) with the fixes of the mentioned issues. > > > > Thanks, > > Duong > > >
