Hi,

We Apache IoTDB Community have fixed many bugs based on the 2.4.1 branch.
We want to include these commits in the next release of Ratis.

Here are the list:

RATIS-1763. Purging logs in an ordered manner.
RATIS-1764. [GrpcLogAppender] create parent directory when installSnapshot
RATIS-1765. [GrpcLogAppender] Calculate streaming md5 file-wise when
installSnapshot
RATIS-1767. Initialize MatchIndex to RaftLog.INVALID_LOG_INDEX.
RATIS-1786. Reset the digester of the follower at the beginning of each
file transfer during a InstallSnapshot to avoid snapshot transfer failure


Thanks
----------------------
Xinyu Tan

Kaijie Chen <[email protected]> 于2023年2月27日周一 23:47写道:

> +1,
>
> "Changes required for Ozone certificate improvements (RATIS-1747,
> RATIS-1753)"
> sounds like a new feature, shall we call it 2.5.0?
>
> Kaijie
>
>
>
> ---- On Mon, 27 Feb 2023 23:08:04 +0800  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
>
>

Reply via email to