OpenSearch/core
Boaz Leskes adb49efe17
Non-peer recovery should set the global checkpoint (#27965)
Non-Peer recoveries should restore the global checkpoint rather than wait for the activation of the primary. This brings us a step closer to a universe where a recovered shard always has a valid global checkpoint. Concretely:

1) Recovery from store can read the checkpoint from the translog
2) Recovery from local shards and snapshots can set the global checkpoint to the local checkpoint as this is the only copy of the shard.
3) Recovery of an empty shard can set it to `NO_OPS_PERFORMED`

Peer recoveries will follow but require more work and thus will have their own PR.

I also used the moment to clean up `IndexShard`'s api around starting the engine and doing recovery from the translog. The current naming are a relic of the past and don't align with the current naming schemes in the engine.
2017-12-22 21:39:12 +01:00
..
cli Fix publication of elasticsearch-cli to Maven 2017-12-17 11:51:18 -05:00
licenses Upgrade to Lucene 7.2.0. (#27910) 2017-12-20 14:17:40 +01:00
src Non-peer recovery should set the global checkpoint (#27965) 2017-12-22 21:39:12 +01:00
build.gradle Tighten which classes can exit 2017-11-21 16:37:41 -05:00