I've had some experience with similar scenarios. As long as you can
maintain quorum through the ZooKeeper changes and the current leader is
defined within the Solr configuration, a single Solr restart should be
sufficient.
Something along these lines should work:
1. Add new ZooKeeper node to ZooK
> If I correctly understand what you're trying to do with the static
> collections, Solr cannot do it directly. If you have collection A in
> cluster 1, and collection A in cluster 2, they are entirely separate and
> cannot be managed as a single collection. Queries and updates sent to
> one clus
> The zookeeper list isn't really the right place for most of this. The
> residents of this list will to have zero knowledge of how Solr uses
> zookeeper. I'm on both lists -- and I'm a lot more familiar with Solr
> than Zookeeper.
I think I see that now. I was under the impression that this mi
I have a very large ZooKeeper cluster which manages config and replication
for multiple SolrCloud clusters. I want to split the monolithic ZooKeeper
cluster into smaller, more manageable clusters in a live migration (i.e.
minimal or no downtime).
I have collections that can be updated dynamically
