I agree. 1. Shut down each Solr server process using the “bin/solr” script. 2. Shut down the Zookeeper ensemble. 3. Take backups. 4. Shut down the OS.
Do that in reverse to get going. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Oct 30, 2018, at 8:03 PM, Erick Erickson <erickerick...@gmail.com> wrote: > > bin/solr stop > > As long as you don't kill it with extreme prejudice (i.e. kill -9 or > pull the plug) it should be fine. Assuming you're running ZooKeeper > in an external ensemble, I'd certainly stop those after all the Solr > instances were stopped. > > Powering the nodes up is irrelevant to Solr, the bin/solr start bit > will actually start the Solr instance. And no, there's nothing special > that needs to happen there, it's just like any other time the script > starts Solr. You'll have to have the ZooKeeper instances running for > Solr to come up of course. > > Best, > Erick > On Tue, Oct 30, 2018 at 2:57 PM 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
