You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Arne Bachmann (JIRA)" <ji...@apache.org> on 2017/04/20 08:11:04 UTC
[jira] [Resolved] (ZOOKEEPER-2764) By default, only srvr
four-letter word is on the whitelist, while documentation says all are
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arne Bachmann resolved ZOOKEEPER-2764.
--------------------------------------
Resolution: Not A Bug
Fix Version/s: 3.5.3
The pointer to the current version's documentation was helpful, I was checking the old version's documentation.
> By default, only srvr four-letter word is on the whitelist, while documentation says all are
> --------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2764
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2764
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.3
> Reporter: Arne Bachmann
> Priority: Minor
> Fix For: 3.5.3
>
>
> Using the same Vagrant provisioning script as for 3.5.2-alpha, suddenly all monitoring tools told me that the ZK instance was unavailable or had an error. Investigating further, the instance was fine as a follower, but the response to telnet "ruok" was actually "ruok ... is not in the whitelist".
> Is this a new default not reflected in the documentation yet? It says since 3.4.10 there's a whitelist option, but all commands are by default on it (same as 4lw.commands.whitelist=*).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)