[ 
https://issues.apache.org/jira/browse/FLINK-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928316#comment-16928316
 ] 

TisonKun edited comment on FLINK-13417 at 9/12/19 7:43 AM:
-----------------------------------------------------------

[~StephanEwen] I figured out that it is because since 3.5.3 ZooKeeper default 
disable four letter words which HBase uses for waiting for server up. We can 
set the property in Flink test scope to enable four letter words and workaround 
this issue. Have patched the fix in private branch and still digging whether 
there are other issues.

references:

[1] https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_4lw
[2] 
https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_clusterOptions 
(look up {{zookeeper.4lw.commands.whitelist}})


was (Author: tison):
[~StephanEwen] I figured out that it is because since 3.5.3 ZooKeeper default 
disable four letter words which HBase uses for waiting for server up. We can 
set the property in Flink test scope to enable four letter words and workaround 
this issue. Have sent the fix and still digging whether there are other issues.

references:

[1] https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_4lw
[2] 
https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_clusterOptions 
(look up {{zookeeper.4lw.commands.whitelist}})

> 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)

Reply via email to