Thanks for driving this. I'm not familiar with the listed advanced Curator configs, but the previous added switch for disabling ensemble tracking [1] saved us when deploying Flink in a cloud env where ZK can only be accessible via URLs. That being said, +1 for the overall idea, these configs may help users in certain scenarios sooner or later.
[1] https://issues.apache.org/jira/browse/FLINK-31780 Best, Zhanghao Chen ________________________________ From: Alex Nitavsky <alexnitav...@gmail.com> Sent: Thursday, December 14, 2023 21:20 To: dev@flink.apache.org <dev@flink.apache.org> Subject: [DISCUSS] FLIP-402: Extend ZooKeeper Curator configurations Hi all, I would like to start a discussion thread for: *FLIP-402: Extend ZooKeeper Curator configurations *[1] * Problem statement * Currently Flink misses several Apache Curator configurations, which could be useful for Flink deployment with ZooKeeper as HA provider. * Proposed solution * We have inspected all possible options for Apache Curator and proposed those which could be valuable for Flink users: - high-availability.zookeeper.client.authorization [2] - high-availability.zookeeper.client.maxCloseWaitMs [3] - high-availability.zookeeper.client.simulatedSessionExpirationPercent [4] The proposed way is to reflect those properties into Flink configuration options for Apache ZooKeeper. Looking forward to your feedback and suggestions. Kind regards Oleksandr [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-402%3A+Extend+ZooKeeper+Curator+configurations [2] https://curator.apache.org/apidocs/org/apache/curator/framework/CuratorFrameworkFactory.Builder.html#authorization(java.lang.String,byte%5B%5D) [3] https://curator.apache.org/apidocs/org/apache/curator/framework/CuratorFrameworkFactory.Builder.html#maxCloseWaitMs(int) [4] https://curator.apache.org/apidocs/org/apache/curator/framework/CuratorFrameworkFactory.Builder.html#simulatedSessionExpirationPercent(int)
