Martijn van Groningen 5fa81310cc

[CCR] Added history uuid validation (#33546) ...

For correctness we need to verify whether the history uuid of the leader
index shards never changes while that index is being followed.

* The history UUIDs are recorded as custom index metadata in the follow index.
* The follow api validates whether the current history UUIDs of the leader
  index shards are the same as the recorded history UUIDs.
  If not the follow api fails.
* While a follow index is following a leader index; shard follow tasks
  on each shard changes api call verify whether their current history uuid
  is the same as the recorded history uuid.

Relates to #30086 

Co-authored-by: Nhat Nguyen <nhat.nguyen@elastic.co>

2018-09-12 19:42:00 +02:00

..

fixtures

Test: Fix forbidden uses in test framework (#32824)

2018-08-14 11:35:09 -07:00

framework

[CCR] Added history uuid validation (#33546)

2018-09-12 19:42:00 +02:00

logger-usage

Consider multi release jars when running third party audit (#33206)

2018-08-29 09:53:04 +03:00

build.gradle

Test: Fix forbidden uses in test framework (#32824)

2018-08-14 11:35:09 -07:00