I think that your approach would work, but you would want to have your "master " server up when you bring the new server online. The new server will become a follower of one of the shards, and get the shard content via replication. Once complete, you could shut down the shard on the "master", and the new server would be promoted automatically to the shard leader.
Sent from my Verizon Wireless 4GLTE smartphone ----- Reply message ----- From: "Jeff Rhines" <rhin...@gmail.com> To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> Subject: [External] Re: how to scale from 1 server to 3 servers with 3 shards Date: Thu, Nov 8, 2012 7:30 am It's my understanding that your strategy is correct, although I expect that zookeeper would need to be updated somehow with the new second and third shards, no? On Nov 8, 2012, at 2:36 AM, SuoNayi <suonayi2...@163.com> wrote: > Hi all, > Because it' unable to add or remove shard after solrcloud cluster is > initialized, > so we have to predict a precise shard size at first, saying we need 3 > shards(0 replica). > But now we have no enough server to set up the cluster with one shard per one > server. > In this situation, I have to set up the cluster on the single server, does > this mean I have to > deploy three solr instances(shards) on the same server with different > directories? > when more servers are available, how to move the rest two shards to the new > servers? > Just copying the files to the new server seems does not work. > Hope someone can give me a hit,thanks a lot. > > > Regards > SuoNayi
