Hi Oleksandr, The FLIP talks about Curator, but outside of flink test utils, the usage of Curator is only for test purposes. I don't think there's anything preventing you right now from providing these additional parameters as values in the flink-conf.yaml ?
Best regards, Martijn On Thu, Dec 14, 2023 at 2:21 PM Alex Nitavsky <alexnitav...@gmail.com> wrote: > > 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)
