You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Xie, Sean" <Se...@finra.org> on 2017/06/16 15:05:30 UTC

Live update the zookeeper for SOLR

Is there a way to keep SOLR alive when zookeeper instances (3 instance ensemble) are rolling updated one at a time? It seems SOLR cluster use one of the zookeeper instance and when the communication is broken in between, it won’t be able to reconnect to another zookeeper instance and keep itself alive. A service restart is need in this situation. Any way to keep the service alive all the time?

Thanks
Sean

Confidentiality Notice::  This email, including attachments, may include non-public, proprietary, confidential or legally privileged information.  If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited.  If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately.  You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.

Re: Live update the zookeeper for SOLR

Posted by Chris Ulicny <cu...@iq.media>.
> It seems SOLR cluster use one of the zookeeper instance

Is solr configured to point to exactly one host or to a list of the hosts
in the zookeeper ensemble? The zkHost value should contain all of the zk
hosts.

We had a similar issue where the solr instance was only pointing to zk1 and
none of the rest. It went down, and that resulted in the solr instance
being inaccessible since it can't find the rest of the zk ensemble.

Best,
Chris

On Fri, Jun 16, 2017 at 11:05 AM Xie, Sean <Se...@finra.org> wrote:

> Is there a way to keep SOLR alive when zookeeper instances (3 instance
> ensemble) are rolling updated one at a time? It seems SOLR cluster use one
> of the zookeeper instance and when the communication is broken in between,
> it won’t be able to reconnect to another zookeeper instance and keep itself
> alive. A service restart is need in this situation. Any way to keep the
> service alive all the time?
>
> Thanks
> Sean
>
> Confidentiality Notice::  This email, including attachments, may include
> non-public, proprietary, confidential or legally privileged information.
> If you are not an intended recipient or an authorized agent of an intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of the information contained in or transmitted with this e-mail is
> unauthorized and strictly prohibited.  If you have received this email in
> error, please notify the sender by replying to this message and permanently
> delete this e-mail, its attachments, and any copies of it immediately.  You
> should not retain, copy or use this e-mail or any attachment for any
> purpose, nor disclose all or any part of the contents to any other person.
> Thank you.
>

Re: Live update the zookeeper for SOLR

Posted by "Xie, Sean" <Se...@finra.org>.
Solr is configured with the zookeeper ensemble as mentioned below.

I will provide logs in a later time.

From: Shawn Heisey <ap...@elyograg.org>>
Date: Friday, Jun 16, 2017, 12:27 PM
To: solr-user@lucene.apache.org <so...@lucene.apache.org>>
Subject: [EXTERNAL] Re: Live update the zookeeper for SOLR

On 6/16/2017 9:05 AM, Xie, Sean wrote:
> Is there a way to keep SOLR alive when zookeeper instances (3 instance
> ensemble) are rolling updated one at a time? It seems SOLR cluster use
> one of the zookeeper instance and when the communication is broken in
> between, it won’t be able to reconnect to another zookeeper instance
> and keep itself alive. A service restart is need in this situation.
> Any way to keep the service alive all the time?

Have you informed Solr about all three of the ZK hosts?  You need a
zkHost like this, with an optional chroot:

zkHost="server1.example.com:2181,server2.example.com:2181,server3.example.com:2181/chroot"

There are more zkHost examples and a better description of the string
format in this javadoc:

https://lucene.apache.org/solr/6_6_0/solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html#CloudSolrClient-java.lang.String-

If Solr hasn't been explicitly informed about all the hosts in the
ensemble, then it cannot connect to surviving hosts.

I've never heard of the problem you described happening as long as
Zookeeper quorum is maintained and Solr is properly configured.

If you can show that a correctly configured Solr 6.6 server loses
connection to ZK when one of the ZK servers is taken down, that's a bug,
and we need an issue in Jira with documentation of the problem.

Thanks,
Shawn

Confidentiality Notice::  This email, including attachments, may include non-public, proprietary, confidential or legally privileged information.  If you are not an intended recipient or an authorized agent of an intended recipient, you are hereby notified that any dissemination, distribution or copying of the information contained in or transmitted with this e-mail is unauthorized and strictly prohibited.  If you have received this email in error, please notify the sender by replying to this message and permanently delete this e-mail, its attachments, and any copies of it immediately.  You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.

Re: Live update the zookeeper for SOLR

Posted by Shawn Heisey <ap...@elyograg.org>.
On 6/16/2017 9:05 AM, Xie, Sean wrote:
> Is there a way to keep SOLR alive when zookeeper instances (3 instance
> ensemble) are rolling updated one at a time? It seems SOLR cluster use
> one of the zookeeper instance and when the communication is broken in
> between, it won’t be able to reconnect to another zookeeper instance
> and keep itself alive. A service restart is need in this situation.
> Any way to keep the service alive all the time?

Have you informed Solr about all three of the ZK hosts?  You need a
zkHost like this, with an optional chroot:

zkHost="server1.example.com:2181,server2.example.com:2181,server3.example.com:2181/chroot"

There are more zkHost examples and a better description of the string
format in this javadoc:

https://lucene.apache.org/solr/6_6_0/solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html#CloudSolrClient-java.lang.String-

If Solr hasn't been explicitly informed about all the hosts in the
ensemble, then it cannot connect to surviving hosts.

I've never heard of the problem you described happening as long as
Zookeeper quorum is maintained and Solr is properly configured.

If you can show that a correctly configured Solr 6.6 server loses
connection to ZK when one of the ZK servers is taken down, that's a bug,
and we need an issue in Jira with documentation of the problem.

Thanks,
Shawn