[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899173#comment-16899173
]
Jan Høydahl commented on SOLR-13672:
------------------------------------
The screenshot shows another error where whitelist is not configured for one of
the zk hosts. The ruok command is the first we try so when it fails we fail the
whole host.
We now explicitly skip the ‘membership:” line.
We are not parsing a config file but text response from a socket call. It’s a
mess, some commands respond with tab separated lines, other with = separated :)
> Admin UI/ZK Status page: Zookeeper 3.5 : 4lw.commands.whitellist error
> ----------------------------------------------------------------------
>
> Key: SOLR-13672
> URL: https://issues.apache.org/jira/browse/SOLR-13672
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.2
> Reporter: Jörn Franke
> Priority: Major
> Attachments: SOLR-13672.patch, zk-status.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After upgrading to Solr 8.2 and Zookeeper 3.5.5 one sees the following error
> in the Admin UI / Cloud / ZkStatus:
> {color:#222222}*"Errors: - membership: Check 4lw.commands.whitelist setting
> in zookeeper{color}
> {color:#222222}configuration file."*{color}
> {color:#222222}Aside of the UI, the Solr Cloud nodes seem to work perfectly
> normal.{color}
> {color:#222222}This issue only occurs with ZooKeeper ensembles. It does not
> appear if one Zookeeper standalone instance is used.{color}
> {color:#222222}We tried the 4lw.commands.whitelist with wildcard * and
> "mntr,conf,ruok" (with and without spaces).{color}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
