(Doc+) link videos for allocation and ilm (elastic#116880) (elastic#1…

…17097) * (Doc+) link videos for allocation and ilm --------- Co-authored-by: shainaraskas <[email protected]>
costin · Nov 19, 2024 · c029282 · c029282
1 parent e241221
commit c029282
Show file tree

Hide file tree

Showing 6 changed files with 21 additions and 4 deletions.
diff --git a/docs/reference/cluster/allocation-explain.asciidoc b/docs/reference/cluster/allocation-explain.asciidoc
@@ -159,6 +159,8 @@ node.
 <5> The decider which led to the `no` decision for the node.
 <6> An explanation as to why the decider returned a `no` decision, with a helpful hint pointing to the setting that led to the decision. In this example, a newly created index has <<indices-get-settings,an index setting>> that requires that it only be allocated to a node named `nonexistent_node`, which does not exist, so the index is unable to allocate.
 
+See https://www.youtube.com/watch?v=5z3n2VgusLE[this video] for a walkthrough of troubleshooting a node and index setting mismatch.
+
 [[maximum-number-of-retries-exceeded]]
 ====== Maximum number of retries exceeded
 
@@ -234,7 +236,9 @@ primary shard that was previously allocated.
 ----
 // NOTCONSOLE
 
-TIP: If a shard is unassigned with an allocation status of `no_valid_shard_copy`, then you should <<fix-cluster-status-recover-nodes,make sure that all nodes are in the cluster>>. If all the nodes containing in-sync copies of a shard are lost, then you can <<fix-cluster-status-restore,recover the data for the shard>>.
+If a shard is unassigned with an allocation status of `no_valid_shard_copy`, then you should <<fix-cluster-status-recover-nodes,make sure that all nodes are in the cluster>>. If all the nodes containing in-sync copies of a shard are lost, then you can <<fix-cluster-status-restore,recover the data for the shard>>. 
+
+See https://www.youtube.com/watch?v=6OAg9IyXFO4[this video] for a walkthrough of troubleshooting `no_valid_shard_copy`.
 
 ===== Unassigned replica shard
 

diff --git a/docs/reference/ilm/error-handling.asciidoc b/docs/reference/ilm/error-handling.asciidoc
@@ -8,8 +8,9 @@ When this happens, {ilm-init} moves the index to an `ERROR` step.
 If {ilm-init} cannot resolve the error automatically, execution is halted  
 until you resolve the underlying issues with the policy, index, or cluster.
 
-See this https://www.youtube.com/watch?v=VCIqkji3IwY[{ilm-init} health video] 
-for example troubleshooting walkthrough.
+See https://www.youtube.com/watch?v=VCIqkji3IwY[this video] 
+for a walkthrough of troubleshooting current {ilm-init} health issues, and https://www.youtube.com/watch?v=onrnnwjYWSQ[this video]
+for a walkthrough of troubleshooting historical {ilm-init} issues.
 
 For example, you might have a `shrink-index` policy that shrinks an index to four shards once it
 is at least five days old: 

diff --git a/docs/reference/snapshot-restore/repository-s3.asciidoc b/docs/reference/snapshot-restore/repository-s3.asciidoc
@@ -6,6 +6,9 @@ You can use AWS S3 as a repository for {ref}/snapshot-restore.html[Snapshot/Rest
 *If you are looking for a hosted solution of Elasticsearch on AWS, please visit
 https://www.elastic.co/cloud/.*
 
+See https://www.youtube.com/watch?v=ACqfyzWf-xs[this video]
+for a walkthrough of connecting an AWS S3 repository.
+
 [[repository-s3-usage]]
 ==== Getting started
 

diff --git a/docs/reference/troubleshooting/common-issues/diagnose-unassigned-shards.asciidoc b/docs/reference/troubleshooting/common-issues/diagnose-unassigned-shards.asciidoc
@@ -8,5 +8,6 @@ In order to diagnose the unassigned shards in your deployment use the following
 
 include::{es-ref-dir}/tab-widgets/troubleshooting/data/diagnose-unassigned-shards-widget.asciidoc[]
 
-
+See https://www.youtube.com/watch?v=v2mbeSd1vTQ[this video]
+for a walkthrough of monitoring allocation health.
 
diff --git a/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc b/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
@@ -19,6 +19,8 @@ operate to have a green health status.
 In many cases, your cluster will recover to green health status automatically. 
 If the cluster doesn't automatically recover, then you must <<fix-red-yellow-cluster-status,manually address>> 
 the remaining problems so management and cleanup activities can proceed.
+See https://www.youtube.com/watch?v=v2mbeSd1vTQ[this video]
+for a walkthrough of monitoring allocation health.
 
 [discrete]
 [[diagnose-cluster-status]]
@@ -90,6 +92,8 @@ PUT _cluster/settings
 }
 ----
 
+See https://www.youtube.com/watch?v=MiKKUdZvwnI[this video] for walkthrough of troubleshooting "no allocations are allowed".
+
 [discrete]
 [[fix-cluster-status-recover-nodes]]
 ===== Recover lost nodes
@@ -262,3 +266,5 @@ POST _cluster/reroute?metric=none
 ----
 // TEST[s/^/PUT my-index\n/]
 // TEST[catch:bad_request]
+
+See https://www.youtube.com/watch?v=6OAg9IyXFO4[this video] for a walkthrough of troubleshooting `no_valid_shard_copy`.
diff --git a/docs/reference/troubleshooting/diagnostic.asciidoc b/docs/reference/troubleshooting/diagnostic.asciidoc
@@ -13,6 +13,8 @@ This information can be used to troubleshoot problems with your cluster. For exa
 You can generate diagnostic information using this tool before you contact https://support.elastic.co[Elastic Support] or 
 https://discuss.elastic.co[Elastic Discuss] to minimize turnaround time. 
 
+See this https://www.youtube.com/watch?v=Bb6SaqhqYHw[this video] for a walkthrough of capturing an {es} diagnostic.
+
 [discrete]
 [[diagnostic-tool-requirements]]
 === Requirements
Original file line number	Diff line number	Diff line change
Expand Up		@@ -8,5 +8,6 @@ In order to diagnose the unassigned shards in your deployment use the following

		include::{es-ref-dir}/tab-widgets/troubleshooting/data/diagnose-unassigned-shards-widget.asciidoc[]


		See https://www.youtube.com/watch?v=v2mbeSd1vTQ[this video]
		for a walkthrough of monitoring allocation health.