Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-15 Thread Andor Molnar
https://issues.apache.org/jira/browse/ZOOKEEPER-3511 Andor -Original Message-From: Patrick Hunt Reply- To: user@zookeeper.apache.orgTo: UserZooKeeper < user@zookeeper.apache.org>Subject: Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0Date: Mon, 5 Aug 2019 09:04:44 -0700 It

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-05 Thread Patrick Hunt
It sounds to me like a regression. We always had the properties format for 4lw, this (membership:) breaks that. I'd recommend fixing it in the next 3.5/3.6. ie. output the membership on a single line "membership: \n". Should be a pretty simple change - anyone interested in taking it on? Also

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-05 Thread Enrico Olivelli
Il lun 5 ago 2019, 00:57 Jan Høydahl ha scritto: > Will admin server be folded in and exposed on same port as main client > port in the future? If not, clients will need to have one config for zkHost > plus one more for zkAdminServer. Personally I hope we won't do this. I hope we continue

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-04 Thread Jan Høydahl
Will admin server be folded in and exposed on same port as main client port in the future? If not, clients will need to have one config for zkHost plus one more for zkAdminServer. I asked in another thread of admin server port number will have a better/more unique default than 8080 in the

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-04 Thread Enrico Olivelli
Il sab 3 ago 2019, 21:41 Shawn Heisey ha scritto: > On 8/2/2019 10:33 AM, Patrick Hunt wrote: > > Right, it prints the membership of the quorum, see (for majority case > which > > is typical): > > org.apache.zookeeper.server.quorum.flexible.QuorumMaj#toString > > >

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-03 Thread Shawn Heisey
On 8/2/2019 10:33 AM, Patrick Hunt wrote: Right, it prints the membership of the quorum, see (for majority case which is typical): org.apache.zookeeper.server.quorum.flexible.QuorumMaj#toString

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-02 Thread Patrick Hunt
On Fri, Aug 2, 2019 at 7:12 AM Jan Høydahl wrote: > So it turned out that Solr failed parsing the 'conf' response from > Zookeeper since there was one line that did not conform to the key=value > syntax: > > ... > quorumPort=2888 > peerType=0 > membership: >

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-08-02 Thread Jan Høydahl
So it turned out that Solr failed parsing the 'conf' response from Zookeeper since there was one line that did not conform to the key=value syntax: ... 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

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-31 Thread Zheng Lin Edwin Yeo
Sure. I have another thread on this in the Solr mailing list. Regards, Edwin On Wed, 31 Jul 2019 at 14:04, Jörn Franke wrote: > Could be a Solr issue. Check the Solr mailing list - they can help you > there better on Solr issues. > > > Am 31.07.2019 um 04:27 schrieb Zheng Lin Edwin Yeo >: > >

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-31 Thread Jörn Franke
Could be a Solr issue. Check the Solr mailing list - they can help you there better on Solr issues. > Am 31.07.2019 um 04:27 schrieb Zheng Lin Edwin Yeo : > > Thanks everyone for your reply. > > I have tried to put the following in zoo.cfg under ZooKeeper: >

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-30 Thread Zheng Lin Edwin Yeo
Thanks everyone for your reply. I have tried to put the following in zoo.cfg under ZooKeeper: 4lw.commands.whitelist=mntr,conf,ruok But it is still showing this error. *"Errors: - membership: Check 4lq.commands.whitelist setting in zookeeper configuration file."* As I am using SolrCloud, the

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-30 Thread Shawn Heisey
On 7/29/2019 11:45 PM, Enrico Olivelli wrote: Due to potential security risks since ZK 3.5 you have to explicitly whitelist some commands. The 3.5.5 documentation says that "*" can be used to whitelist all commands. But what you just said seems to contradict that. If your statement is more

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-30 Thread Enrico Olivelli
Due to potential security risks since ZK 3.5 you have to explicitly whitelist some commands. I think you should contact SolrCloud I hope that helps Enrico Il mar 30 lug 2019, 04:08 Zheng Lin Edwin Yeo ha scritto: > Hi, > > I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper

Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-29 Thread Jörn Franke
Maybe the Solr mailing list should address this. > Am 30.07.2019 um 04:08 schrieb Zheng Lin Edwin Yeo : > > Hi, > > I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper 3.5.5. > > However, after adding in the line under zoo.cfg > *4lw.commands.whitelist=** > > I get the error

Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0

2019-07-29 Thread Zheng Lin Edwin Yeo
Hi, I am using the new Solr 8.2.0 with SolrCloud and external ZooKeeper 3.5.5. However, after adding in the line under zoo.cfg *4lw.commands.whitelist=** I get the error under Cloud -> ZK Status in Solr *"Errors: - membership: Check 4lq.commands.whitelist setting in zookeeper configuration