[
https://issues.apache.org/jira/browse/FLINK-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943594#comment-16943594
]
Zili Chen commented on FLINK-13417:
-----------------------------------
Hello Stephan, the situation is actually flink-runtime uses
zookeeper(flink-mesos used a wrapper version of curator's shared value which
satisfy use through a utility way) so thay I think the way you proposed is
worth to try.
However, there's one prerequisite of this way. That's we need to bump
curator-test to 4.x(related FLINK-10052) because curator-test 2.x uses zk 3.4
for starting server so that create container message from zk 2.5 client cannot
be identified.
> Bump Zookeeper to 3.5.5
> -----------------------
>
> Key: FLINK-13417
> URL: https://issues.apache.org/jira/browse/FLINK-13417
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.9.0
> Reporter: Konstantin Knauf
> Priority: Major
> Fix For: 1.10.0
>
>
> User might want to secure their Zookeeper connection via SSL.
> This requires a Zookeeper version >= 3.5.1. We might as well try to bump it
> to 3.5.5, which is the latest version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
