Hi,
Our indexer before starting does upload/reload of Solr configuration files
using ZK UPLOAD and RELOAD APIs. In this process zookeeper is not
stopped/restarted. ZK is alive and so are Solr nodes.
Doing this often causes following exception. Kindly note that the ZK
instance is standalone and not
On 7/27/2015 10:59 PM, Modassar Ather wrote:
> If we upgrade zookeeper we need to restart. This upgrade process is
> automated for future releases/changes of zookeeper.
> This is a single external zookeeper which is completely stopped/shutdown.
> No Solr node are restarted/shutdown.
> What I have u
If we upgrade zookeeper we need to restart. This upgrade process is
automated for future releases/changes of zookeeper.
This is a single external zookeeper which is completely stopped/shutdown.
No Solr node are restarted/shutdown.
What I have understanding that even if the zookeeper shuts down, aft
On 7/27/2015 10:21 PM, Modassar Ather wrote:
> Erick I am using the ZK upload process only. It is just that it is added
> into a script.
> The exception is coming when I am doing a RELOAD of collection after the ZK
> restart and fresh schema/solrconfig is uploaded.
> And once this exception occurs
Erick I am using the ZK upload process only. It is just that it is added
into a script.
The exception is coming when I am doing a RELOAD of collection after the ZK
restart and fresh schema/solrconfig is uploaded.
And once this exception occurs I have to restart the Solr nodes to get them
working.
Why are you doing this? It seems like you're making it
_much_ more difficult than necessary. Sure, automate
all the non-solr stuff, but why not make your scripts use
the ZK upload/download process that's well established
and tested for maintaining the Solr specific data?
Best,
Erick
On Mon, Jul 2
Thanks for your response Erick and Shawn.
We had automated the solr/zookeeper future upgrades using scripts. So for
any new version of solr/zookeeper we use those script.
While upgrading zookeeper we do stop it to install it as a service and then
apply the new distribution(which is currently 3.4.6
On 7/27/2015 6:17 AM, Modassar Ather wrote:
> Kindly help me understand following with respect to Solr version 5.2.1.
>
> 1. What happens to the solr cluster if the standalone external zookeeper is
> stopped/restarted with some changes done in zoo_data during the restart?
> E.g After restartin
Frankly, I do not know. I would reload all my collections
as a preventative measure though. I'm no sure that this
is a scenario that's been actively supported and therefore
would not rely on rebooting Zookeeper to cause all my
collections to reload (and thus get, say, any config changes).
Actually
