Thanks Mark,
I've looked at these, as well as these configuration parameters.
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards
However, I've not been able to find a configuration that actually
accomplishes what we're looking
It's not a bug, ES allocates based on higher level primary shard count and
doesn't take into account what index a shard may belong to, this is where
allocation awareness and routing comes into play.
Take a look at
Hi All,
We have several indexes in our ES cluster. ES is not our canonical
system record, we use it only for searching.
Some of our applications have very high write throughput, so for these we
allocate a singular primary shard for each of our nodes. For example, we
have 6 nodes, and we
