Re: Volounteers for releases ?

Hi all, Sorry for the disruption. I want to ask if there is any possibility for us to include [ZOOKEEPER-4471][1] and [ZOOKEEPER-4472][2] in 3.9.0. ZOOKEEPER-4472 proposed to add `WatcherType.Persistent` and `WatcherType.PersistentRecursive` to remove `AddWatchMode.PERSISTENT` and `AddWatchMode.

Review request for ZOOKEEPER-4471 and ZOOKEEPER-4472

Hi all and committers, [ZOOKEEPER-4471][1] reported that `AddWatchMode.PERSISTENT` could be partially removed by `WatcherType.Data` or `WatcherType.Children`. [ZOOKEEPER-4472][2] proposed to add `WatcherType.Persistent` and `WatcherType.PersistentRecursive` to remove `AddWatchMode.PERSISTENT` and

[jira] [Created] (ZOOKEEPER-4704) Flaky test: ReconfigRollingRestartCompatibilityTest.testRollingRestartWithExtendedMembershipConfig

Kezhu Wang created ZOOKEEPER-4704: - Summary: Flaky test: ReconfigRollingRestartCompatibilityTest.testRollingRestartWithExtendedMembershipConfig Key: ZOOKEEPER-4704 URL: https://issues.apache.org/jira/browse/ZOOKEE

Re: FIPS: removing ZKTrustManager

"we use this method dozens of other places in the code" Checked. Mostly logging and output formatting like 4lws, etc. On Sat, 2023-06-10 at 11:18 +0200, Andor Molnar wrote: > First, I've created a pull request for ZOOKEEPER-3860: > > https://github.com/apache/zookeeper/pull/2005 > > To improv

Re: FIPS: removing ZKTrustManager

First, I've created a pull request for ZOOKEEPER-3860: https://github.com/apache/zookeeper/pull/2005 To improve the logging in ZKTrustManager without altering the behaviour. The patch also contains a change in NetUtils.formatInetAddr() which, I believe, should use the hostname when creating textu