I was expecting some of the shards to relocate to the new node but I can understand the reason it didn't happen could be because the versions are different.
My assumption (I am going to test this theory) is if all the nodes are on the same version then the shards would get distributed across two nodes PS: My deployment is like two master node with data On Wednesday, March 4, 2015 at 12:42:25 AM UTC-8, Mark Walkom wrote: > > It sounds like standard behaviour. > > What do expect to happen? > > On 4 March 2015 at 17:35, Suresh Ramkrishnaiah <[email protected] > <javascript:>> wrote: > >> I had a single node es database on 1.3 and added another node with 1.4 >> all the shards replicated onto the new node but they didn't get >> reallocated. >> >> Is this the default default behavior? >> >> I am wondering what's the best way to reallocate the shards? or should I >> just terminate the old node so that the new node becomes primary? >> >> >> Thanks, >> Suresh >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/ba55b528-8d07-4ea9-b862-93e2173d033c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/ba55b528-8d07-4ea9-b862-93e2173d033c%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/df23b06a-5596-4f35-8f29-ed8563fcdbd4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
