Hi Nikolas,
We tried the following:
{
"persistent": {
"cluster": {
"routing": {
"allocation": {
"balance": {
"index": "0.05",
"shard": "0.05",
"primary": "0.9",
"threshold": "1.0"
}
}
}
}
},
"transient": {}
}
And it doesn't seem to do much... also when we trigger the movement of
shards manually, it only moves that shard and nothing else. Doesn't cause
a big rebalance. It seems to still balance 2 out of the 5 nodes with
primaries while the other two have only replicas.
Is there anything we're missing?
Thanks!
On Wednesday, July 23, 2014 9:30:00 AM UTC-4, Nikolas Everett wrote:
On Wed, Jul 23, 2014 at 9:21 AM, <mic...@modernmast.com <javascript:>>
wrote:Thanks for that, Nik. I'm okay with evenly spreading all the indices,
rather than just the one I'm having issues with. I'll give your config a
try!Def no special configurations on that one. We didn't even realize there
was such a thing as allocation configuration up until yesterday (after the
0/6 allocation happened). The 0/6 node did, however, contain 4/6
replicas... If that makes a difference?It certainly does. The way the allocation settings are configured now the
cluster thinks of replicas as just about the same as masters. For the most
part they are, too. For us they certainly are.If you are sure that being a shard master is significantly more work then
being a shard replica then raise the "primary" setting to something like .5
and lower everything else to total 1.That whole totally 1 thing isn't required but it makes the numbers easier
to think about.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/86ef9e5c-01f8-4733-913e-1ac2f851deb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.