honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Restores do not cause red health (#59015) 

Since 2.0.0 (56a264cf6d) we have documented that restoring a snapshot
typically results in `red` cluster health. However since 5.0.0 (#19516)
this hasn't been true, we report `yellow` health for unassigned
primaries that will be recovered from a snapshot in the future. This
commit adjusts these docs to match today's behaviour.
This commit is contained in:
David Turner 2020-07-04 11:16:02 +01:00
parent e88d71b187
commit 2fdd8f3a2c
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/reference/snapshot-restore/monitor-snapshot-restore.asciidoc
View File

@ -48,13 +48,14 @@ GET /_snapshot/my_backup/snapshot_1/_status
While snapshot info method returns only basic information about the snapshot in progress, the snapshot status returns While snapshot info method returns only basic information about the snapshot in progress, the snapshot status returns
complete breakdown of the current state for each shard participating in the snapshot. complete breakdown of the current state for each shard participating in the snapshot.
The restore process piggybacks on the standard recovery mechanism of the Elasticsearch. As a result, standard recovery The restore process piggybacks on the standard recovery mechanism of the
monitoring services can be used to monitor the state of restore. When restore operation is executed the cluster Elasticsearch. As a result, standard recovery monitoring services can be used
typically goes into `red` state. It happens because the restore operation starts with "recovering" primary shards of the to monitor the state of restore. When the restore operation is executed the
restored indices. During this operation the primary shards become unavailable which manifests itself in the `red` cluster cluster typically goes into `yellow` state because the restore operation works
state. Once recovery of primary shards is completed Elasticsearch is switching to standard replication process that by recovering primary shards of the restored indices. Once the recovery of the
creates the required number of replicas at this moment cluster switches to the `yellow` state. Once all required replicas primary shards is completed Elasticsearch switches to the standard replication
are created, the cluster switches to the `green` states. process that creates the required number of replicas. Once all required
replicas are created, the cluster switches to the `green` states.
The cluster health operation provides only a high level status of the restore process. It's possible to get more The cluster health operation provides only a high level status of the restore process. It's possible to get more
detailed insight into the current state of the recovery process by using <<indices-recovery, index recovery>> and detailed insight into the current state of the recovery process by using <<indices-recovery, index recovery>> and