zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <ph...@apache.org>
Subject Re: Issues with using ZooKeeper 3.5.5 together with Solr 8.2.0
Date Fri, 02 Aug 2019 16:33:15 GMT
On Fri, Aug 2, 2019 at 7:12 AM Jan Høydahl <jan.asf@cominvent.com> 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:
> 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
> ...
>
> The "membership: " line was the offender here. Can anyone shed some light
> on the purpose of that line? Is it a header for what comes in the lines
> below or is it a key with wrong delimiter (: instead of =)? and empty value?
>
>
Right, it prints the membership of the quorum, see (for majority case which
is typical):
org.apache.zookeeper.server.quorum.flexible.QuorumMaj#toString
https://github.com/apache/zookeeper/blob/faa7cec71fddfb959a7d67923acffdb67d93c953/zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/flexible/QuorumMaj.java#L112

Seems like the header, it came in from a change by @Alexander Shraer
<shralex@gmail.com> who may have more insight.

Patrick


> We'll fix the parsing in Solr to disregard this line for now.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> > 31. jul. 2019 kl. 08:34 skrev Zheng Lin Edwin Yeo <edwinyeozl@gmail.com
> >:
> >
> > 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 <jornfranke@gmail.com> 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 <
> edwinyeozl@gmail.com
> >>> :
> >>>
> >>> 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 collection config can still be loaded to
> >>> ZooKeeper as per normal. But if I tried to create a collection, I will
> >> get
> >>> the following error:
> >>>
> >>> {
> >>> "responseHeader":{
> >>>   "status":400,
> >>>   "QTime":686},
> >>> "failure":{
> >>>   "192.168.1.2:8983
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at: http://192.168.1.2:8983/solr",
> >>>   "192.168.1.2:8984
> >> _solr":"org.apache.solr.client.solrj.SolrServerException:IOException
> >>> occurred when talking to server at: http://192.168.1.2:8984/solr"},
> >>> "Operation create caused
> >>>
> >>
> exception:":"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException:
> >>> Underlying core creation failed while creating collection:
> collection1",
> >>> "exception":{f
> >>>   "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>>   "rspCode":400},
> >>> "error":{
> >>>   "metadata":[
> >>>     "error-class","org.apache.solr.common.SolrException",
> >>>     "root-error-class","org.apache.solr.common.SolrException"],
> >>>   "msg":"Underlying core creation failed while creating collection:
> >>> collection1",
> >>>   "code":400}}
> >>>
> >>> Is there anything which I may have missed out?
> >>>
> >>> Regards,
> >>> Edwin
> >>>
> >>>> On Wed, 31 Jul 2019 at 00:12, Shawn Heisey <apache@elyograg.org>
> wrote:
> >>>>
> >>>>> 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 accurate, then the documentation should be updated to list the
> >>>> commands that are NOT enabled when using a wildcard.
> >>>>
> >>>> There is a SOLR issue to upgrade the client in Solr to 3.5.5:
> >>>>
> >>>> https://issues.apache.org/jira/browse/SOLR-8346
> >>>>
> >>>> A comment was made on this issue saying that the following config is
> >>>> needed when the server is running 3.5.x:
> >>>>
> >>>> 4lw.commands.whitelist=mntr,conf,ruok
> >>>>
> >>>> Thanks,
> >>>> Shawn
> >>>>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message