What I notice is that while re-balancing the nodes are re balancing the
indices not the shards within it?
I was expecting the shards to get rebalanced.
Now Index 1 has all the shards in Node 1, whereas Index 2 has all the 5
shards in Node 2.
Shards are being evened out, index is not really taken into account (and thats the problem you are running into). Thats how ES works now, and you can work a bit around it by shards_per_node setting. It will be improved in the very near future.
What I notice is that while re-balancing the nodes are re balancing the indices not the shards within it?
I was expecting the shards to get rebalanced.
Now Index 1 has all the shards in Node 1, whereas Index 2 has all the 5 shards in Node 2.
Is this an expected behavior?
Thanks
Rahul
On Sun, Aug 5, 2012 at 5:33 PM, Rahul Sharma rahul.sharma.coder@gmail.com wrote:
That was it!!
Thanks a lot Clint. Appreciate your quick response.
Aah I see.
Just FYI, Indexes created afterwards got distributed correctly.
On Wed, Aug 8, 2012 at 3:26 AM, Shay Banon kimchy@gmail.com wrote:
Shards are being evened out, index is not really taken into account (and
thats the problem you are running into). Thats how ES works now, and you
can work a bit around it by shards_per_node setting. It will be improved in
the very near future.
What I notice is that while re-balancing the nodes are re balancing the
indices not the shards within it?
I was expecting the shards to get rebalanced.
Now Index 1 has all the shards in Node 1, whereas Index 2 has all the 5
shards in Node 2.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.