Hi, Yes, zookeeper is external, and yes, we'll definitely wait until after solr has stopped to bring it down.
Thanks for the tip about disabling `autoAddReplicas`, we definitely don't want the shards moving around during the process. Wunder, your point 3 mentions "take backups". Given that our data is on hdfs (not co-located with the solr servers) and backed up separately, what else would you recommend backing up? The contents of the `solr.home.home` folder seem like good candidates... anything else? Let's say one of the servers gets dropped during the move, is it sufficient to restore the contents of `solr.home.home` onto a new server with the same hostname/solrVersion/zookeeperConfig and bring it up in the same way as the others? Thanks all, Kyle On Wed, 31 Oct 2018 at 05:22, Shalin Shekhar Mangar <shalinman...@gmail.com> wrote: > In case you are using a recent Solr 7.x version with collections that have > autoAddReplicas=true, you should disable the auto add replicas feature > before powering off so that Solr does not decide to move replicas around > because nodes have been lost. See > > https://lucene.apache.org/solr/guide/7_4/solrcloud-autoscaling-auto-add-replicas.html#using-cluster-property-to-enable-autoaddreplicas > > On Wed, Oct 31, 2018 at 3:27 AM lstusr 5u93n4 <lstusr...@gmail.com> wrote: > > > Hi All, > > > > We have a solr cloud running 3 shards, 3 hosts, 6 total NRT replicas, and > > the data director on hdfs. It has 950 million documents in the index, > > occupying 700GB of disk space. > > > > We need to completely power off the system to move it. > > > > Are there any actions we should take on shutdown to help the process? > > Anyhing we should expect on power on? > > > > Thanks, > > > > Kyle > > > > > -- > Regards, > Shalin Shekhar Mangar. >
