When shards are evenly distributed, they won't move again. What you should do is to start the two nodes, set replica to 1, the kill node 2 and set replica to 0.
Or you use the cluster reroute API: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-reroute.html David > Le 5 févr. 2015 à 22:40, Steve Johnson <[email protected]> a écrit : > > I have a single ES AWS instance that I've been logging to as part of a > standard ELK stack. It has been running for about 4 weeks. I had replication > disabled. > > Today, I decided to stop and start the instance so that I could increase the > memory size of the it. When it came back up, only about half of the 5 shards > for each index were assigned...in some cases two, and in some cases 3. > > After fooling around a bunch, I looked on the disk, where I found that each > of my indexes were stored within two high-level directories, > '/data1/elasticsearch/es-vpc3/nodes/0' and > /data1/elasticsearch/es-vpc3/nodes/1'. It is the shards stored in the '0' > directory that were being assigned. The shards stored in '1' were not. This > indicated to me that I must have been running two ES instances on the one > instance without knowing it. So I figured, 'what the heck', and I started a > second copy of ES. Sure enough, my other shards were assigned to the second > instance! > > Here's the problem though. I've been using the HEAD plugin to view my > cluster. Prior to the reboot, the display represented the cluster as a single > ES instance with all of the shards being shown together in a single row. Now, > I get two rows, one for each instance of ES, with the appropriate nodes for > what I saw in the directory structure shown in each of the two rows. So > something is clearly different than it was before. It appears that I was not > running two distinct instances of ES. So what was I doing? Why did my indexes > get split across two "nodes/N" directories and why upon reboot did only the > "nodes/0" shards get assigned? > > Can someone tell me what is going on here....what was different about my > setup before and after the reboot? Surely just giving the machine more > memory couldn't have caused this, right? > > TIA for any enlightenment. > > -- > 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/3aac59f7-30b9-40fc-af61-6de6c0764d6e%40googlegroups.com. > 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/E47DA4B9-AB6B-4BDD-9912-95496A928096%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
