From 7c4fc9050e8db23cb53b96e1f2ae518a700e0445 Mon Sep 17 00:00:00 2001 From: Stef Nestor <26751266+stefnestor@users.noreply.github.com> Date: Thu, 23 May 2024 10:48:47 -0600 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Ievgen Degtiarenko --- .../common-issues/red-yellow-cluster-status.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc b/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc index 47c7e9cc3c5ea..4b49e191f4e16 100644 --- a/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc +++ b/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc @@ -220,10 +220,9 @@ don't exist or are irrecoverable, <> will report `no_valid_shard_copy` and you'll need to do one of the following: * restore the missing data from <> -* re-add the missind data from its original data source +* index the missing data from its original data source * accept data loss on the index-level by running <> -* accept data loss on the shard-level by running <> with -`accept_data_loss: true` +* accept data loss on the shard-level by executing <> allocate_stale_primary or allocate_empty_primary command with `accept_data_loss: true` + WARNING: Only use this option if node recovery is no longer possible. This process allocates an empty primary shard. If the node later rejoins the cluster,