Another batch

marciw · marciw · commit 64b14a421eb8 · 2025-02-10T09:40:48.000-05:00
diff --git a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Corrupted repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-corrupted-repositories.html
 ---
diff --git a/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md b/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Invalid repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-invalid-repositories.html
 ---
diff --git a/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md b/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Unknown repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-unknown-repositories.html
 ---
diff --git a/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/java.md b/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/java.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Java
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/troubleshooting.html
 ---
 
-# Java [troubleshooting]
+# Troubleshoot {{es}} Java client [troubleshooting]
 
 
 ## Exceptions [_exceptions] 
diff --git a/troubleshoot/elasticsearch/elasticsearch-client-javascript-api/nodejs.md b/troubleshoot/elasticsearch/elasticsearch-client-javascript-api/nodejs.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Node.js
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/timeout-best-practices.html
 ---
 
-# Node.js [timeout-best-practices]
+# Troubleshoot {{es}} Node.js client [timeout-best-practices]
 
 Starting in 9.0.0, this client is configured to not time out any HTTP request by default. {{es}} will always eventually respond to any request, even if it takes several minutes. Reissuing a request that it has not responded to yet can cause performance side effects. See the [official {{es}} recommendations for HTTP clients](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#_http_client_configuration) for more information.
 
diff --git a/troubleshoot/elasticsearch/elasticsearch-client-net-api/net.md b/troubleshoot/elasticsearch/elasticsearch-client-net-api/net.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: .NET
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/troubleshooting.html
 ---
 
-# .NET [troubleshooting]
+# Troubleshoot {{es}} .NET client [troubleshooting]
 
 The client can provide rich details about what occurred in the request pipeline during the process of making a request, as well as be configured to provide the raw request and response JSON
 
diff --git a/troubleshoot/elasticsearch/elasticsearch-client-ruby-api/ruby.md b/troubleshoot/elasticsearch/elasticsearch-client-ruby-api/ruby.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Ruby
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/client/ruby-api/current/troubleshooting.html
 ---
 
-# Ruby [troubleshooting]
+# Troubleshoot {{es}} Ruby client [troubleshooting]
 
 Use the information in this section to troubleshoot common problems and find answers for frequently asked questions.
 
diff --git a/troubleshoot/elasticsearch/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md b/troubleshoot/elasticsearch/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Apache Hadoop
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/hadoop/current/troubleshooting.html
 ---
 
-# Elasticsearch for Apache Hadoop [troubleshooting]
+# Troubleshoot Elasticsearch for Apache Hadoop [troubleshooting]
 
 Unfortunately, sometimes things do not go as expected and your elasticsearch-hadoop job execution might go awry: incorrect data might be read or written, the job might take significantly longer than expected or you might face some exception. This section tries to provide help and tips for doing your own diagnostics, identifying the problem and hopefully fixing it.
 
diff --git a/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md b/troubleshoot/elasticsearch/elasticsearch-reference/index-lifecycle-management-errors.md
@@ -1,9 +1,12 @@
 ---
+navgiation_title: Index lifecycle management errors
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-error-handling.html
 ---
 
-# Index lifecycle management errors [index-lifecycle-error-handling]
+% marciw move so this is with other ILM topics
+
+# Fix index lifecycle management errors [index-lifecycle-error-handling]
 
 When [{{ilm-init}}](../../../manage-data/lifecycle/index-lifecycle-management.md) executes a lifecycle policy, it’s possible for errors to occur while performing the necessary index operations for a step. 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.
 
diff --git a/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md b/troubleshoot/elasticsearch/elasticsearch-reference/remote-clusters.md
@@ -1,12 +1,12 @@
 ---
-navigation_title: "Troubleshooting"
+navigation_title: Remote clusters
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/remote-clusters-troubleshooting.html
 ---
 
 
 
-# Remote clusters [remote-clusters-troubleshooting]
+# Troubleshoot remote clusters [remote-clusters-troubleshooting]
 
 
 You may encounter several issues when setting up a remote cluster for {{ccr}} or {{ccs}}.
diff --git a/troubleshoot/elasticsearch/fix-data-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-data-node-out-of-disk.md
@@ -1,8 +1,11 @@
 ---
+navigation_title: Data nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-data-node-out-of-disk.html
 ---
 
+% marciw move to new "out of disk" subsection
+
 # Fix data nodes out of disk [fix-data-node-out-of-disk]
 
 {{es}} is using data nodes to distribute your data inside the cluster. If one or more of these nodes are running out of space, {{es}} takes action to redistribute your data within the nodes so all nodes have enough available disk space. If {{es}} cannot facilitate enough available space in a node, then you will need to intervene in one of two ways:
diff --git a/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-master-node-out-of-disk.md
@@ -1,8 +1,11 @@
 ---
+navigation_title: Master nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-master-node-out-of-disk.html
 ---
 
+% marciw move to new "out of disk" subsection
+
 # Fix master nodes out of disk [fix-master-node-out-of-disk]
 
 {{es}} is using master nodes to coordinate the cluster. If the master or any master eligible nodes are running out of space, you need to ensure that they have enough disk space to function. If the [health API](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html) reports that your master node is out of space you need to increase the disk capacity of your master nodes.
diff --git a/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-other-node-out-of-disk.md
@@ -1,8 +1,11 @@
 ---
+navigation_title: Other nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-other-node-out-of-disk.html
 ---
 
+% marciw move to new "out of disk" subsection
+
 # Fix other role nodes out of disk [fix-other-node-out-of-disk]
 
 {{es}} can use dedicated nodes to execute other functions apart from storing data or coordinating the cluster, for example machine learning. If one or more of these nodes are running out of space, you need to ensure that they have enough disk space to function. If the [health API](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html) reports that a node that is not a master and does not contain data is out of space you need to increase the disk capacity of this node.
diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Not enough nodes to allocate shard replicas
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-tier-capacity.html
 ---
diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Snapshot policy failures
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/repeated-snapshot-failures.html
 ---
diff --git a/troubleshoot/elasticsearch/start-ilm.md b/troubleshoot/elasticsearch/start-ilm.md
@@ -1,10 +1,14 @@
 ---
+navigation_title: Index lifecycle management
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-ilm.html
 ---
 
 # Start index lifecycle management [start-ilm]
 
+% marciw consider moving out of troubleshooting and into how-tos
+% marciw or add troubleshooting info from elsewhere
+
 Automatic index lifecycle and data retention management is currently disabled.
 
 In order to start the automatic {{ilm}} service, follow these steps:
diff --git a/troubleshoot/elasticsearch/start-slm.md b/troubleshoot/elasticsearch/start-slm.md
@@ -1,8 +1,12 @@
 ---
+navigation_title: Snapshot lifecycle management
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-slm.html
 ---
 
+% marciw consider moving out of troubleshooting and into how-tos
+% marciw or add troubleshooting info from elsewhere
+
 # Start snapshot lifecycle management [start-slm]
 
 Automatic snapshot lifecycle management is currently disabled. New backup snapshots will not be created automatically.
diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md
@@ -1,9 +1,11 @@
 ---
-navigation_title: Unbalanced cluster
+navigation_title: Unbalanced clusters
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unbalanced-cluster.html
 ---
 
+% marciw move so this is with other cluster topics
+
 # Troubleshoot an unbalanced cluster [troubleshooting-unbalanced-cluster]
 
 Elasticsearch balances shards across data tiers to achieve a good compromise between:
diff --git a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md
@@ -1,5 +1,5 @@
 ---
-navigation_title: Unstable cluster
+navigation_title: Unstable clusters
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unstable-cluster.html
 ---

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Corrupted repositories`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-corrupted-repositories.html`
`4`	`5`	`---`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Invalid repositories`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-invalid-repositories.html`
`4`	`5`	`---`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Unknown repositories`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-unknown-repositories.html`
`4`	`5`	`---`