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 pramodEbay <pr...@ebay.com> on 2015/09/30 01:59:48 UTC
Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Hi,
Is there an example which I could use - to upload solr.xml in zookeeper and
change zkhost entries on the fly and have solr instances be updated via
zookeeper. This will prevent us from restarting each solr node everytime, a
new zookeeper host is added or deleted.
We are on Solr 4.8.
Thanks,
Pramod
--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-8-Updating-zkhost-list-in-solr-xml-without-requiring-a-restart-tp4231979.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Posted by pramodEbay <pr...@ebay.com>.
> The idea is that your list of zookeeper hostnames is a virtual one, not
> a real one.
Thanks for the suggestion. Looks like I am not alone in thinking along the
same lines. I am planning on doing that and was not sure if anyone else
tried this approach and validated that it worked.
--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-8-Updating-zkhost-list-in-solr-xml-without-requiring-a-restart-tp4231979p4232045.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Posted by Upayavira <uv...@odoko.co.uk>.
Why don't you create DNS names, or such, so that you can replace a
zookeeper instance at the same hostname:port rather than having to edit
solr.xml across your whole Solr farm?
The idea is that your list of zookeeper hostnames is a virtual one, not
a real one.
Upayavira
On Wed, Sep 30, 2015, at 04:40 AM, pramodmm wrote:
>
> > Before we even think about upgrading the zookeeper functionality in
> > Solr, we must wait for the official 3.5 release from the zookeeper
> > project. Alpha (or Beta) software will not be included in Solr unless
> > it is the only way to fix a very serious bug. This is a new feature,
> > not a bug.
>
> In the meantime, please help me validate what we are doing is right.
> Currently, our zookeeper instances are running on vmware machines and
> when
> one of them dies and we get a new machine as a replacement - we install
> zookeeper and make it a part of the ensemble. Then we manually, go to
> every
> individual solr instance in the solr cloud - edit its solr.xml - remove
> the
> entry of the dead machine from zkhost and replace it with the new
> hostname -
> thus keeping the list up-to-date. Then, we restart solr box.
>
> Are these the right steps ?
>
> Thanks,
> Pramod
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-4-8-Updating-zkhost-list-in-solr-xml-without-requiring-a-restart-tp4231979p4231994.html
> Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Posted by Shawn Heisey <ap...@elyograg.org>.
On 9/29/2015 9:40 PM, pramodmm wrote:
> In the meantime, please help me validate what we are doing is right.
> Currently, our zookeeper instances are running on vmware machines and when
> one of them dies and we get a new machine as a replacement - we install
> zookeeper and make it a part of the ensemble. Then we manually, go to every
> individual solr instance in the solr cloud - edit its solr.xml - remove the
> entry of the dead machine from zkhost and replace it with the new hostname -
> thus keeping the list up-to-date. Then, we restart solr box.
That sounds correct to me.
It will be very nice for large installs when we can upgrade to ZK 3.5 in
Solr. In order to use the new functionality, the ZK servers must also
be upgraded.
Thanks,
Shawn
Re: Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Posted by pramodmm <pr...@yahoo.com>.
> Before we even think about upgrading the zookeeper functionality in
> Solr, we must wait for the official 3.5 release from the zookeeper
> project. Alpha (or Beta) software will not be included in Solr unless
> it is the only way to fix a very serious bug. This is a new feature,
> not a bug.
In the meantime, please help me validate what we are doing is right.
Currently, our zookeeper instances are running on vmware machines and when
one of them dies and we get a new machine as a replacement - we install
zookeeper and make it a part of the ensemble. Then we manually, go to every
individual solr instance in the solr cloud - edit its solr.xml - remove the
entry of the dead machine from zkhost and replace it with the new hostname -
thus keeping the list up-to-date. Then, we restart solr box.
Are these the right steps ?
Thanks,
Pramod
--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-8-Updating-zkhost-list-in-solr-xml-without-requiring-a-restart-tp4231979p4231994.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 4.8 - Updating zkhost list in solr.xml without requiring a
restart
Posted by Shawn Heisey <ap...@elyograg.org>.
On 9/29/2015 5:59 PM, pramodEbay wrote:
> Is there an example which I could use - to upload solr.xml in zookeeper and
> change zkhost entries on the fly and have solr instances be updated via
> zookeeper. This will prevent us from restarting each solr node everytime, a
> new zookeeper host is added or deleted.
>
> We are on Solr 4.8.
Support in zookeeper for dynamically changing the cluster membership has
been added to the 3.5 version, which is currently only available as an
alpha release.
https://issues.apache.org/jira/browse/ZOOKEEPER-107
This feature has been under development for a REALLY long time. The
comments are a discussion that is very technical in nature and difficult
to follow, it looks like it took a very long time to come up with a
usable design.
I don't know anything about how they have implemented the dynamic
cluster support, so I do not know whether Solr requires code changes to
use it. A quick scan of the first few comments suggests that they are
trying to make this server-side, with all clients updating
automatically, so Solr might not need any code changes. Let's hope that
this is the case.
Before we even think about upgrading the zookeeper functionality in
Solr, we must wait for the official 3.5 release from the zookeeper
project. Alpha (or Beta) software will not be included in Solr unless
it is the only way to fix a very serious bug. This is a new feature,
not a bug.
Thanks,
Shawn