Hmm, so I've been looking around and saw that rebalancing replica shards
isn't something that can be done?
It is the case the primaries are balanced, but the replicas are overloaded
on 1 machine in a 4 machine cluster.
Is there something I need to do, or can do to make them rebalance?
On Friday, March 16, 2012 7:10:05 PM UTC-7, John Cwikla wrote:
We have a 4 node cluster with 1 index, 25m docs or so. We have many
processes reading/writing to our cluster through
pyes which we've verified randomly chooses an initial node to talk to.
Strange thing is, 3 of the 4 nodes are bored (0.25 load), 1 node is taking
the brunt -
40-50 load (16 core).
We can't figure out why - any pointers? Anything I can do to debug what is
going on?
On Friday, March 16, 2012 7:10:05 PM UTC-7, John Cwikla wrote:
We have a 4 node cluster with 1 index, 25m docs or so. We have many
processes reading/writing to our cluster through
pyes which we've verified randomly chooses an initial node to talk to.
Strange thing is, 3 of the 4 nodes are bored (0.25 load), 1 node is taking
the brunt -
40-50 load (16 core).
We can't figure out why - any pointers? Anything I can do to debug what is
going on?
On Friday, March 16, 2012 7:10:05 PM UTC-7, John Cwikla wrote:
We have a 4 node cluster with 1 index, 25m docs or so. We have many
processes reading/writing to our cluster through
pyes which we've verified randomly chooses an initial node to talk to.
Strange thing is, 3 of the 4 nodes are bored (0.25 load), 1 node is taking
the brunt -
40-50 load (16 core).
We can't figure out why - any pointers? Anything I can do to debug what is
going on?