Hi Attila,
Thanks for starting this discussion, I want to include linearizable read related commits in the next release of Ratis. Here is the list: RATIS-1643. Add heartbeat broadcast mechanism for leader readIndex RATIS-1696. Support linearizable read-only requests in leader RATIS-1701. Add new Server RPC: readIndex RATIS-1706. Move heartbeat listeners to LeaderState RATIS-1715. Support linearizable read in AsyncApi RATIS-1716. Separate ReadException and ReadIndexException for client retry RATIS-1758. Add linearizable read in Counter example RATIS-1759. Support client use linearizable read per request RATIS-1773. Fix readIndexHeartbeat using incorrct index handle onAppendEntriesReply method RATIS-1778. Fix NPE in readIndexHeartbeats BTW, since linearizable read is a relatively large feature, should we directly use 2.5.0 as the next release version number. Regards, Yaolong At 2023-02-27 23:08:04, "Attila Doroszlai" <[email protected]> wrote: >Hi all, > >I would like to propose preparing maintenance releases of Ratis >Third-party and Ratis with the following changes since 1.0.3 and >2.4.1, respectively: > >Ratis Thirdparty 1.0.4 >* RATIS-1760. Bump Netty to 4.1.86.Final to fix CVE-2022-41881 > >Ratis 2.4.2 >* RATIS-1748. Cache getMetricName to reduce garbage >* Changes required for Ozone certificate improvements (RATIS-1747, RATIS-1753) >* RATIS-1745. Improve performance of AwaitForSignal by reducing amount >of exceptions created >* RATIS-1754. Set leader to null when stepping down >* RATIS-1756. Consistent usage of gapThreshold in getMajorityMin >* RATIS-1776. Switch to slf4j-reload4j >* RATIS-1792. Replace parallelStream usage in PeerProxyMap > >Is there any other fix that should be backported from master to branch-2? > >thanks, >Attila
