Another batch

Author: marciw

troubleshoot/elasticsearch/allow-all-index-allocation.md

@@ -4,6 +4,9 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-index-allocation.html
 ---
 
+% Need to retitle to be about the problem, not the solution
+% New subsection about unassigned shards?
+
 # Allow Elasticsearch to allocate the index [allow-all-index-allocation]
 
 The allocation of data can be controlled using the [enable allocation configuration](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-modules.html#index-routing-allocation-enable-setting). In certain circumstances users might want to temporarily disable or restrict the allocation of data.

troubleshoot/elasticsearch/diagnose-unassigned-shards.md

@@ -4,6 +4,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnose-unassigned-shards.html
 ---
 
+% marciw move to a new Unassigned shards subsection
+
 # Diagnose unassigned shards [diagnose-unassigned-shards]
 
 There are multiple reasons why shards might get unassigned, ranging from misconfigured allocation settings to lack of disk space.

troubleshoot/elasticsearch/diagnostic.md

@@ -1,11 +1,9 @@
 ---
-navigation_title: "Capture diagnostics"
+navigation_title: "Diagnostics"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnostic.html
 ---
 
-
-
 # Capture diagnostics [diagnostic]
 
 

troubleshoot/elasticsearch/high-cpu-usage.md

@@ -1,9 +1,10 @@
 ---
+navigation_title: High CPU usage
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/high-cpu-usage.html
 ---
 
-# High CPU usage [high-cpu-usage]
+# Symptom: High CPU usage [high-cpu-usage]
 
 {{es}} uses [thread pools](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html) to manage CPU resources for concurrent operations. High CPU usage typically means one or more thread pools are running low.
 

troubleshoot/elasticsearch/increase-cluster-shard-limit.md

@@ -4,6 +4,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-cluster-shard-limit.html
 ---
 
+% marciw move to a new Unassigned shards subsection
+
 # Total number of shards per node has been reached [increase-cluster-shard-limit]
 
 Elasticsearch tries to take advantage of all the available resources by distributing data (index shards) amongst the cluster nodes.

troubleshoot/elasticsearch/increase-shard-limit.md

@@ -4,6 +4,8 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-shard-limit.html
 ---
 
+% marciw retitle; move to a new Unassigned shards subsection
+
 # Total number of shards for an index on a single node exceeded [increase-shard-limit]
 
 Elasticsearch tries to take advantage of all the available resources by distributing data (index shards) among nodes in the cluster.