Question about new shard allocation rules on new nodes


#1

Is there an allocation setting that allows a node to participate in balancing but not allow new shards to be allocated to it? I've found that when I add a new node that it gets a disproportionate amount of new shards, overloading it. I have a number of indices that turn over hourly and daily so it would be nice to not have to set allocation rules at the index level. It would also be nice to get away from what I do now, allocating a large number of empty shards to then new node to match the shard count of the other nodes and delete them slowly over days until they're gone and the cluster is balanced.
Any ideas or settings I've missed?

~Lane


(Mike Simos) #2

You probably can accomplish something using tags:

https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules-allocation.html

If you had a tag for each machine, then you could exclude any new machine from getting any new shards. Then later on you could remove the exclude tag if you wanted to.


#3

Thank you.


(system) #4