As my understand, you mean that we can just add replicas for the already existent shards. This step is straight.After replicas are active, we can just shutdown the replaced shard nodes and new leaders will be present automatically. right? At last we just remove the stuff left on those replaced shard nodes,but why we need unload the cores on the replaced machines?
At 2013-01-26 09:52:14,"Mark Miller" <markrmil...@gmail.com> wrote: >You could do it that way. > >I'm not sure why you are worried about the leaders. That shouldn't matter. > >You could also start up new Solrs on the new machines as replicas of the cores >you want to move - then once they are active, unload the cores on the old >machine, stop the Solr instances and remove the stuff left on the filesystem. > >- Mark > >On Jan 25, 2013, at 7:42 PM, Mingfeng Yang <mfy...@wisewindow.com> wrote: > >> Right now I have an index with four shards on a single EC2 server, each >> running on different ports. Now I'd like to migrate three shards >> to independent servers. >> >> What should I do to safely accomplish this process? >> >> Can I just >> 1. shutdown all four solr instances. >> 2. copy three shards (indexes) to different servers. >> 3. launch 4 solr instances on 4 different servers, each with -zKhost >> specified, pointing to the zookeeper servers. >> >> In my impression, zookeeper remembers which shards are leaders. What I >> plan to do above could not elect the three new servers as leaders. If so, >> what's the correct way to do it? >> >> Thanks, >> Ming >
