Hi, if you're using 3.5.0 you could consider reconfiguring the cluster, e.g. remove the servers under maintanance and add them back after you're done. The removal is logical - they will still continue serving clients unless shut down, its just these servers will not be counted - a majority of the remaining servers will be needed.
Alex On Fri, Jan 9, 2015 at 12:50 AM, Kambiz Niktabar <[email protected] > wrote: > Hi, > We are using ZooKepper ensembles to manage configuration files of our Solr > environment. Basically our servers are distributed to two different > physical locations (e.g. Site A and Site B) which every location has its > own maintenance window for security patching, etc. That means during the > maintenance time, it might happens that all servers in site A will be > unavailable.Since the majority of ZooKeeper instances needs to be up and > running to have ZooKeeper available, this forces us to perform maintenance > on the site with minority instances manually.I wonder if there is any smart > way to setup Zookeeper to have fully redundant service for these two > location without involving any manual job?please advise > RegardsKambiz Niktabar
