[
https://issues.apache.org/jira/browse/FLINK-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921386#comment-16921386
]
TisonKun commented on FLINK-13417:
----------------------------------
[~till.rohrmann]
Here is [the
thread|https://lists.apache.org/x/thread.html/a35ef4da607121ac3621f7eee01b377b4d205b6bf676357bd25d949f@%3Cuser.zookeeper.apache.org%3E]
as well as the upgrade FAQ
[page|https://cwiki.apache.org/confluence/display/ZOOKEEPER/Upgrade+FAQ].
It is announced no intended or known break changes if we upgrade zk to 3.5 and
require quorums running on 3.5. But if we upgrade to zk 3.5, since we would
like to make used of {{CreateMode.CONTAINER}} the packet won't be identified by
a 3.4 server and will fail with {{KeeperException.UnimplementedException}}.
Simply sum up, the upgrade should not cost any changes in FLINK side but
required our users running FLINK against zk 3.5 servers. Unless we add an
switch to opt-in and opt-out, with manually fallback the use of new features
introduced in 3.5.
> 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: Blocker
> 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.2#803003)
