[jira] [Commented] (SOLR-13672) Admin UI/ZK Status page: Zookeeper 3.5 : 4lw.commands.whitellist error

["Jan Høydahl (JIRA)" <ji...@apache.org>]

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

Jan Høydahl commented on SOLR-13672:
------------------------------------

Ok, I reproduced it here. Apparently 3.5.5 has some new format of the response in `conf` 4lw command, e.g.:
{noformat}
clientPort=2181
secureClientPort=-1
dataDir=/data/version-2
dataDirSize=201326640
dataLogDir=/datalog/version-2
dataLogSize=582
tickTime=2000
maxClientCnxns=60
minSessionTimeout=4000
maxSessionTimeout=40000
serverId=1
initLimit=5
syncLimit=2
electionAlg=3
electionPort=3888
quorumPort=2888
peerType=0
membership: 
server.1=zoo1:2888:3888:participant;0.0.0.0:2181
server.2=zoo2:2888:3888:participant;0.0.0.0:2181
server.3=zoo3:2888:3888:participant;0.0.0.0:2181
version=0Connection closed by foreign host.
{noformat}
Obviously the parsing logic expects strictly {{key=value}} for each line, but there is a line here that is only {{membership:}} which I believe causes some parsing error in {{ZookeeperStatusHandler}}

> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org