[
https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898913#comment-16898913
]
Jan Høydahl commented on SOLR-13672:
------------------------------------
Sorry, did not see your patch since I was working on PR [GitHub Pull Request
#818|https://github.com/apache/lucene-solr/pull/818]
The "membership: " line looks like a header line for the server.N lines that
follows. Or it could possibly be that is is supposed to have a value and they
used wrong separator. Anyway, my PR explicitly skip that line and print
warnings for other unknown/malformed lines found in the future.
I decided to also make visible a few of the new configs in the UI. Here's how
the page now looks like if it finds two good zk servers and one which is not
configured with whitelist:
!zk-status.png!
> 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: [email protected]
For additional commands, e-mail: [email protected]
