[ https://issues.apache.org/jira/browse/SOLR-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899263#comment-16899263 ]
Jan Høydahl commented on SOLR-13672: ------------------------------------ PR reviews welcome. Hope to merge next week. PS. There’s an email thread on zk list about why that membership: line exists, may perhaps lead to a ZK Jira, but anyway, the parsing logic is now more robust. Earlier we aborted everything if a line did not have a separator, now we instead log it but continue. > 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