Armin Braun 85be78b624

Fix Snapshot Abort Not Waiting for Data Nodes (#58214) (#58228) ...

This was a really subtle bug that we introduced a long time ago.
If a shard snapshot is in aborted state but hasn't started snapshotting on a node
we can only send the failed notification for it if the shard was actually supposed
to execute on the local node.
Without this fix, if shard snapshots were spread out across at least two data nodes
(so that each data node does not have all the primaries) the abort would actually
never wait on the data nodes. This isn't a big deal with uuid shard generations
but could lead to potential corruption on S3 when using numeric shard generations
(albeit very unlikely now that we have the 3 minute wait there).
Another negative side-effect of this bug was that master would receive a lot more
shard status update messages for aborted shards since each data node not assigned
a primary would send one message for that primary.

2020-06-17 11:39:50 +02:00

..

licenses

Update to lucene snapshot e7c625430ed (#57981)

2020-06-11 14:51:53 +01:00

src

Fix Snapshot Abort Not Waiting for Data Nodes (#58214) (#58228)

2020-06-17 11:39:50 +02:00

build.gradle

Remove deprecated usage of testCompile configuration (#57921) (#58083)

2020-06-14 22:30:44 +02:00