Ali Beyad c5b6f52ecc Fixes maintaining the shards a snapshot is waiting on (#24289) ...

There was a bug in the calculation of the shards that a snapshot must
wait on, due to their relocating or initializing, before the snapshot
can proceed safely to snapshot the shard data.  In this bug, an
incorrect key was used to look up the index of the waiting shards,
resulting in the fact that each index would have at most one shard in
the waiting state causing the snapshot to pause.  This could be
problematic if there are more than one shard in the relocating or
initializing state, which would result in a snapshot prematurely
starting because it thinks its only waiting on one relocating or
initializing shard (when in fact there could be more than one).  While
not a common case and likely rare in practice, it is still problematic.

This commit fixes the issue by ensuring the correct key is used to look
up the waiting indices map as it is being built up, so the list of
waiting shards for each index (those shards that are relocating or
initializing) are aggregated for a given index instead of overwritten.

2017-04-24 10:59:08 -04:00

..

licenses

Upgrade to a Lucene 7 snapshot (#24089)

2017-04-18 15:17:21 +02:00

src

Fixes maintaining the shards a snapshot is waiting on (#24289)

2017-04-24 10:59:08 -04:00

build.gradle

Build: Switch jna dependency to an elastic version (#24081)

2017-04-13 00:17:50 -07:00