diff --git a/troubleshoot/elasticsearch/add-repository.md b/troubleshoot/elasticsearch/add-repository.md index acca0fc44..695f9413b 100644 --- a/troubleshoot/elasticsearch/add-repository.md +++ b/troubleshoot/elasticsearch/add-repository.md @@ -1,9 +1,10 @@ --- +navigation_title: Broken repositories mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/add-repository.html --- -# Troubleshooting broken repositories [add-repository] +# Troubleshoot broken repositories [add-repository] There are several situations where the [Health API](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html) might report an issue regarding the integrity of snapshot repositories in the cluster. The following pages explain the recommended actions for diagnosing corrupted, unknown, and invalid repositories: diff --git a/troubleshoot/elasticsearch/add-tier.md b/troubleshoot/elasticsearch/add-tier.md index 141db4ddf..59c871fbb 100644 --- a/troubleshoot/elasticsearch/add-tier.md +++ b/troubleshoot/elasticsearch/add-tier.md @@ -1,9 +1,14 @@ --- +navigation_title: Index allocation data tier mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/add-tier.html --- -# Add a missing tier to the system [add-tier] +% marciw move this page to a new index allocation subsection +% or just move it down in the ToC +% and this page really really needs rewriting + +# Add a preferred data tier to a deployment [add-tier] The allocation of indices in an {{es}} deployment can be allocated on [data tiers](../../manage-data/lifecycle/data-tiers.md). diff --git a/troubleshoot/elasticsearch/allow-all-cluster-allocation.md b/troubleshoot/elasticsearch/allow-all-cluster-allocation.md index cc8114fa7..9daa090ab 100644 --- a/troubleshoot/elasticsearch/allow-all-cluster-allocation.md +++ b/troubleshoot/elasticsearch/allow-all-cluster-allocation.md @@ -1,5 +1,6 @@ --- -mapped_pages: +navigation_title: Data allocation +mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-cluster-allocation.html --- diff --git a/troubleshoot/elasticsearch/allow-all-index-allocation.md b/troubleshoot/elasticsearch/allow-all-index-allocation.md index cc192ddbf..5de4878ad 100644 --- a/troubleshoot/elasticsearch/allow-all-index-allocation.md +++ b/troubleshoot/elasticsearch/allow-all-index-allocation.md @@ -1,8 +1,12 @@ --- +navigation_title: Index allocation 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. diff --git a/troubleshoot/elasticsearch/corruption-troubleshooting.md b/troubleshoot/elasticsearch/corruption-troubleshooting.md index 5b21f7f24..1941e59a7 100644 --- a/troubleshoot/elasticsearch/corruption-troubleshooting.md +++ b/troubleshoot/elasticsearch/corruption-troubleshooting.md @@ -1,9 +1,10 @@ --- +navigation_title: Data corruption mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/corruption-troubleshooting.html --- -# Troubleshooting corruption [corruption-troubleshooting] +# Troubleshoot data corruption [corruption-troubleshooting] {{es}} expects that the data it reads from disk is exactly the data it previously wrote. If it detects that the data on disk is different from what it wrote then it will report some kind of exception such as: diff --git a/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md b/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md index 8a2e08e9a..f08becb2b 100644 --- a/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md +++ b/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md @@ -1,4 +1,5 @@ --- +navigation_title: Decrease disk usage mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/decrease-disk-usage-data-node.html --- diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md index 86962b341..34ad91e3a 100644 --- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md +++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md @@ -1,8 +1,11 @@ --- +navigation_title: Unassigned shards 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. diff --git a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md index 9523ee734..c923d170e 100644 --- a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md +++ b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md @@ -1,9 +1,10 @@ --- +navigation_title: Corrupted repositories mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-corrupted-repositories.html --- -# Diagnosing corrupted repositories [diagnosing-corrupted-repositories] +# Diagnose corrupted repositories [diagnosing-corrupted-repositories] Multiple {{es}} deployments are writing to the same snapshot repository. {{es}} doesn’t support this configuration and only one cluster is allowed to write to the same repository. See [Repository contents](../../deploy-manage/tools/snapshot-and-restore.md#snapshot-repository-contents) for potential side-effects of corruption of the repository contents, which may not be resolved by the following guide. To remedy the situation mark the repository as read-only or remove it from all the other deployments, and re-add (recreate) the repository in the current deployment: diff --git a/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md b/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md index 6d90e4cdf..370d5d754 100644 --- a/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md +++ b/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md @@ -1,9 +1,10 @@ --- +navigation_title: Invalid repositories mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-invalid-repositories.html --- -# Diagnosing invalid repositories [diagnosing-invalid-repositories] +# Diagnose invalid repositories [diagnosing-invalid-repositories] When an {{es}} node faces an unexpected exception when trying to instantiate a snapshot repository, it will mark the repository as "invalid" and write a warning to the log file. Use the following steps to diagnose the underlying cause of this issue: diff --git a/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md b/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md index 9ad19eb20..1d71c1c84 100644 --- a/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md +++ b/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md @@ -1,9 +1,10 @@ --- +navigation_title: Unknown repositories mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-unknown-repositories.html --- -# Diagnosing unknown repositories [diagnosing-unknown-repositories] +# Diagnose unknown repositories [diagnosing-unknown-repositories] When a snapshot repository is marked as "unknown", it means that an {{es}} node is unable to instantiate the repository due to an unknown repository type. This is usually caused by a missing plugin on the node. Make sure each node in the cluster has the required plugins by following the following steps: diff --git a/troubleshoot/elasticsearch/diagnostic.md b/troubleshoot/elasticsearch/diagnostic.md index ff3f9d819..7e0bc53ef 100644 --- a/troubleshoot/elasticsearch/diagnostic.md +++ b/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] diff --git a/troubleshoot/elasticsearch/discovery-troubleshooting.md b/troubleshoot/elasticsearch/discovery-troubleshooting.md index 3c1ae86d2..4a454a398 100644 --- a/troubleshoot/elasticsearch/discovery-troubleshooting.md +++ b/troubleshoot/elasticsearch/discovery-troubleshooting.md @@ -1,9 +1,10 @@ --- +navigation_title: Discovery mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-troubleshooting.html --- -# Troubleshooting discovery [discovery-troubleshooting] +# Troubleshoot discovery [discovery-troubleshooting] In most cases, the discovery and election process completes quickly, and the master node remains elected for a long period of time. diff --git a/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/java.md b/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/java.md index fe9509740..90e6a0208 100644 --- 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 index 32d7c0fd6..c1a0f0aff 100644 --- 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 index def8c4411..34edd2d0d 100644 --- 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 index 6c0bc8638..61cad1878 100644 --- 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 index baf6b1318..9cb0409d0 100644 --- 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 index 22c00897f..f77e653d0 100644 --- 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 index 3ab5980aa..68106b938 100644 --- 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/elasticsearch-reference/security.md b/troubleshoot/elasticsearch/elasticsearch-reference/security.md index 49eb8b27f..f4db2c440 100644 --- a/troubleshoot/elasticsearch/elasticsearch-reference/security.md +++ b/troubleshoot/elasticsearch/elasticsearch-reference/security.md @@ -1,13 +1,12 @@ --- -navigation_title: "Troubleshooting" +navigation_title: Security mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/security-troubleshooting.html --- +% marciw: this page needs to move to the security folder - -# Security [security-troubleshooting] - +# Troubleshoot {{es}} security [security-troubleshooting] Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. diff --git a/troubleshoot/elasticsearch/fix-common-cluster-issues.md b/troubleshoot/elasticsearch/fix-common-cluster-issues.md index 52100d401..1efd9d8bd 100644 --- a/troubleshoot/elasticsearch/fix-common-cluster-issues.md +++ b/troubleshoot/elasticsearch/fix-common-cluster-issues.md @@ -1,4 +1,5 @@ --- +navigation_title: Common cluster issues mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-common-cluster-issues.html --- diff --git a/troubleshoot/elasticsearch/fix-data-node-out-of-disk.md b/troubleshoot/elasticsearch/fix-data-node-out-of-disk.md index 34801c80e..5ef24f88e 100644 --- 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 index 4a30b2605..b7c8662d7 100644 --- 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 index 141856133..136dac52c 100644 --- 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/high-cpu-usage.md b/troubleshoot/elasticsearch/high-cpu-usage.md index 1420ed7df..31d17bbef 100644 --- a/troubleshoot/elasticsearch/high-cpu-usage.md +++ b/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. diff --git a/troubleshoot/elasticsearch/increase-capacity-data-node.md b/troubleshoot/elasticsearch/increase-capacity-data-node.md index 8c40f1668..5b7c40757 100644 --- a/troubleshoot/elasticsearch/increase-capacity-data-node.md +++ b/troubleshoot/elasticsearch/increase-capacity-data-node.md @@ -1,4 +1,5 @@ --- +navigation_title: Increase disk capacity mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-capacity-data-node.html --- diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md index 1657cf3db..65496c265 100644 --- a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md @@ -1,8 +1,11 @@ --- +navigation_title: Total number of shards per node reached 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. diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md index 03d0495bc..f726b8d2b 100644 --- a/troubleshoot/elasticsearch/increase-shard-limit.md +++ b/troubleshoot/elasticsearch/increase-shard-limit.md @@ -1,8 +1,11 @@ --- +navigation_title: Total number of shards for an index exceeded 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. diff --git a/troubleshoot/elasticsearch/increase-tier-capacity.md b/troubleshoot/elasticsearch/increase-tier-capacity.md index d347a5cb0..f66ab7f8d 100644 --- a/troubleshoot/elasticsearch/increase-tier-capacity.md +++ b/troubleshoot/elasticsearch/increase-tier-capacity.md @@ -1,9 +1,10 @@ --- +navigation_title: Not enough nodes to allocate shard replicas mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-tier-capacity.html --- -# Not enough nodes to allocate all shard replicas [increase-tier-capacity] +# Warning: Not enough nodes to allocate all shard replicas [increase-tier-capacity] Distributing copies of the data (index shard replicas) on different nodes can parallelize processing requests thus speeding up search queries. This can be achieved by increasing the number of replica shards up to the maximum value (total number of nodes minus one) which also serves the purpose to protect against hardware failure. If the index has a preferred tier, Elasticsearch will only place the copies of the data for that index on nodes in the target tier. diff --git a/troubleshoot/elasticsearch/monitoring-troubleshooting.md b/troubleshoot/elasticsearch/monitoring-troubleshooting.md index 81a65154e..0c4cbf563 100644 --- a/troubleshoot/elasticsearch/monitoring-troubleshooting.md +++ b/troubleshoot/elasticsearch/monitoring-troubleshooting.md @@ -1,9 +1,10 @@ --- +navigation_title: Monitoring mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-troubleshooting.html --- -# Troubleshooting monitoring [monitoring-troubleshooting] +# Troubleshoot monitoring [monitoring-troubleshooting] Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. See also [Troubleshooting monitoring in {{ls}}](https://www.elastic.co/guide/en/logstash/current/monitoring-troubleshooting.html). diff --git a/troubleshoot/elasticsearch/red-yellow-cluster-status.md b/troubleshoot/elasticsearch/red-yellow-cluster-status.md index 5d7e7cb59..629bf256b 100644 --- a/troubleshoot/elasticsearch/red-yellow-cluster-status.md +++ b/troubleshoot/elasticsearch/red-yellow-cluster-status.md @@ -1,4 +1,5 @@ --- +navigation_title: Red or yellow health status mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html --- diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md index 6cf73ca2a..7e9df29a0 100644 --- a/troubleshoot/elasticsearch/repeated-snapshot-failures.md +++ b/troubleshoot/elasticsearch/repeated-snapshot-failures.md @@ -1,9 +1,10 @@ --- +navigation_title: Snapshot policy failures mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/repeated-snapshot-failures.html --- -# Addressing repeated snapshot policy failures [repeated-snapshot-failures] +# Fix repeated snapshot policy failures [repeated-snapshot-failures] Repeated snapshot failures are usually an indicator of a problem with your deployment. Continuous failures of automated snapshots can leave a deployment without recovery options in cases of data loss or outages. diff --git a/troubleshoot/elasticsearch/start-ilm.md b/troubleshoot/elasticsearch/start-ilm.md index e88923f13..8d7e05da1 100644 --- 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 index fff61df1a..f2810c25d 100644 --- a/troubleshoot/elasticsearch/start-slm.md +++ b/troubleshoot/elasticsearch/start-slm.md @@ -1,9 +1,13 @@ --- +navigation_title: Snapshot lifecycle management mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-slm.html --- -# Start Snapshot Lifecycle Management [start-slm] +% 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/transform-troubleshooting.md b/troubleshoot/elasticsearch/transform-troubleshooting.md index 7b666c8df..1109291e7 100644 --- a/troubleshoot/elasticsearch/transform-troubleshooting.md +++ b/troubleshoot/elasticsearch/transform-troubleshooting.md @@ -1,9 +1,10 @@ --- +navigation_title: Transforms mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-troubleshooting.html --- -# Troubleshooting transforms [transform-troubleshooting] +# Troubleshoot transforms [transform-troubleshooting] Use the information in this section to troubleshoot common problems. diff --git a/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md b/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md index 790dfafe6..3db96a97f 100644 --- a/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md +++ b/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md @@ -1,9 +1,12 @@ --- +navigation_title: Incomplete migration to data tiers mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshoot-migrate-to-tiers.html --- -# Indices mix index allocation filters with data tiers node roles to move through data tiers [troubleshoot-migrate-to-tiers] +% old title: Mix of index allocation filters and data tier node roles + +# Troubleshoot incomplete migration to data tiers [troubleshoot-migrate-to-tiers] Elasticsearch standardized the implementation of [hot-warm-cold architectures](https://www.elastic.co/blog/elasticsearch-data-lifecycle-management-with-data-tiers) to [data tiers](../../manage-data/lifecycle/data-tiers.md) in version 7.10. Some indices and deployments might have not fully transitioned to [data tiers](../../manage-data/lifecycle/data-tiers.md) and mix the new way of implementing the hot-warm-cold architecture with [legacy](../../deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/index-level-shard-allocation.md) based node attributes. diff --git a/troubleshoot/elasticsearch/troubleshooting-searches.md b/troubleshoot/elasticsearch/troubleshooting-searches.md index 15ccc8b7d..3de0a6172 100644 --- a/troubleshoot/elasticsearch/troubleshooting-searches.md +++ b/troubleshoot/elasticsearch/troubleshooting-searches.md @@ -1,9 +1,10 @@ --- +navigation_title: Searches mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-searches.html --- -# Troubleshooting searches [troubleshooting-searches] +# Troubleshoot searches [troubleshooting-searches] When you query your data, Elasticsearch may return an error, no search results, or results in an unexpected order. This guide describes how to troubleshoot searches. diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md index cf0780676..8fd0941c2 100644 --- a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md +++ b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md @@ -1,9 +1,10 @@ --- +navigation_title: Shard capacity issues mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-shards-capacity-issues.html --- -# Troubleshooting shards capacity health issues [troubleshooting-shards-capacity-issues] +# Troubleshoot shard capacity health issues [troubleshooting-shards-capacity-issues] {{es}} limits the maximum number of shards to be held per node using the [`cluster.max_shards_per_node`](https://www.elastic.co/guide/en/elasticsearch/reference/current/misc-cluster-settings.html#cluster-max-shards-per-node) and [`cluster.max_shards_per_node.frozen`](https://www.elastic.co/guide/en/elasticsearch/reference/current/misc-cluster-settings.html#cluster-max-shards-per-node-frozen) settings. The current shards capacity of the cluster is available in the [health API shards capacity section](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html#health-api-response-details-shards-capacity). diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md index 319dd5873..d43a4f385 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md @@ -1,9 +1,12 @@ --- +navigation_title: Unbalanced clusters mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unbalanced-cluster.html --- -# Troubleshooting an unbalanced cluster [troubleshooting-unbalanced-cluster] +% 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 index 707052560..4cc009261 100644 --- a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md +++ b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md @@ -1,9 +1,10 @@ --- +navigation_title: Unstable clusters mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unstable-cluster.html --- -# Troubleshooting an unstable cluster [troubleshooting-unstable-cluster] +# Troubleshoot an unstable cluster [troubleshooting-unstable-cluster] Normally, a node will only leave a cluster if deliberately shut down. If a node leaves the cluster unexpectedly, it’s important to address the cause. A cluster in which nodes leave unexpectedly is unstable and can create several issues. For instance: diff --git a/troubleshoot/elasticsearch/watcher-troubleshooting.md b/troubleshoot/elasticsearch/watcher-troubleshooting.md index 72e27f534..a686eba98 100644 --- a/troubleshoot/elasticsearch/watcher-troubleshooting.md +++ b/troubleshoot/elasticsearch/watcher-troubleshooting.md @@ -1,9 +1,10 @@ --- +navigation_title: Watcher mapped_pages: - https://www.elastic.co/guide/en/elasticsearch/reference/current/watcher-troubleshooting.html --- -# Troubleshooting Watcher [watcher-troubleshooting] +# Troubleshoot Watcher [watcher-troubleshooting] ## Dynamic mapping error when trying to add a watch [_dynamic_mapping_error_when_trying_to_add_a_watch] diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml index 4126cdb56..f70366f76 100644 --- a/troubleshoot/toc.yml +++ b/troubleshoot/toc.yml @@ -15,9 +15,9 @@ toc: - file: elasticsearch/mapping-explosion.md - file: elasticsearch/hotspotting.md - file: elasticsearch/diagnose-unassigned-shards.md - - file: elasticsearch/add-tier.md - file: elasticsearch/allow-all-cluster-allocation.md - file: elasticsearch/allow-all-index-allocation.md + - file: elasticsearch/add-tier.md - file: elasticsearch/troubleshoot-migrate-to-tiers.md - file: elasticsearch/increase-tier-capacity.md - file: elasticsearch/increase-shard-limit.md