Try setting "indices.recovery.max_bytes_per_sec" much higher for faster
recovery. The default is 20mb/s, and there's a bug in versions prior to 1.2
that rate limit to even lower than that. You didn't specify how big your
indices are, but I can fairly accurately predict how long it'll take for
t
On Wed, Jun 25, 2014 at 8:05 AM, James Carr wrote:
> I launched two new EC2 instances to join the cluster and watched. Some
> shards began relocating, no big deal. Six hours later I checked in and
> some shards were still locating, one shard was recovering. Weird but
> whatever... the cluster hea
Earlier this week we discovered that our three node elasticsearch
cluster needed to be expanded as it was getting dangerously close to
maximum capacity. I was nervous about this and read up the best I
could on best practices to doing this. The only information I seemed
to be able to find is to ensu
