On Sun, Aug 3, 2014 at 7:43 PM, Mark Walkom <ma...@campaignmonitor.com> wrote:
> Shard size will depend entirely on how many shards you've set and how big > the index is. > Allocation of data to shards happens in a round-robin manner, so balancing > isn't needed. > > What do you mean by shards changing in the background? > > The shards aren't assigned round robin - they are assigned to minimize a cluster balance function. The cluster balance function is a combination of three independent functions described here: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards None of them take into account shard size. I'm working on one right now that does. For now your best bet is to set cluster.routing.allocation.balance.index pretty high, like 80% of the sum. That'll make all shards of a given index are smoothed across all nodes. The new one will try to balance the count of shards of similar size across all the nodes. That keeps one node from filling up while the others only have small shards, for example. It should also spread load more evenly when the indexes are different sizes. Nik -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3ah7gtmJJkHKmi9hNncU%3D8E5%3DcdLrb2LjyrBaeOZnyiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
