Removed doc doesn't add much value and combined 2 similar errors into one. Other small changes as well

Author: thekofimensah

troubleshoot/elasticsearch.md

@@ -30,6 +30,12 @@ If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps si
 * [](/troubleshoot/elasticsearch/increase-cluster-shard-limit.md)
 * [](/troubleshoot/elasticsearch/corruption-troubleshooting.md)
 
+## Errors [troubleshooting-errors]
+
+* [](/troubleshoot/elasticsearch/all-shards-failed.md)
+* [](/troubleshoot/elasticsearch/failed-to-parse-field-of-type.md)
+* [](/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md)
+* [](/troubleshoot/elasticsearch/unable-to-parse-response-body.md)
 
 ## Management [troubleshooting-management]
 

troubleshoot/elasticsearch/all-shards-failed.md

@@ -6,8 +6,7 @@ applies_to:
     ess: 
     ece: 
     self: 
-navigation_title: "Error: All shards failed"
-# is mapped_pages needed for newly created docs?
+navigation_title: "Error: all shards failed"
 ---
 
 # Fix error: All shards failed [all-shards-failed]

troubleshoot/elasticsearch/data.md

@@ -15,7 +15,6 @@ Use the topics in this section to troubleshoot data-related issues in your {{es}
 * [](/troubleshoot/elasticsearch/increase-cluster-shard-limit.md)
 * [](/troubleshoot/elasticsearch/corruption-troubleshooting.md)
 
-
 ## Additional resources
 * [](/troubleshoot/elasticsearch/fix-watermark-errors.md)
 * [Troubleshooting overview](/troubleshoot/index.md)

troubleshoot/elasticsearch/errors.md

@@ -10,5 +10,3 @@ Use the topics in this section to troubleshoot common errors in {{es}} deploymen
 * [](/troubleshoot/elasticsearch/failed-to-parse-field-of-type.md)
 * [](/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md)
 * [](/troubleshoot/elasticsearch/unable-to-parse-response-body.md)
-* [](/troubleshoot/elasticsearch/updating-number-of-replicas-to-for-indices.md)
-* [](/troubleshoot/elasticsearch/memory-locking-error.md)

troubleshoot/elasticsearch/failed-to-parse-field-of-type.md

@@ -6,8 +6,7 @@ applies_to:
     ess: 
     ece: 
     self: 
-navigation_title: "Error: failed to parse field of type in document with id"
-# is mapped_pages needed for newly created docs?
+navigation_title: "Error: Failed to parse field of type in document with id"
 ---
 
 # Fix error: Failed to parse field [failed-to-parse-field-of-type]
@@ -50,16 +49,10 @@ PUT test
 }
 ```
 
-## Troubleshoot and resolve the error
+To check the data type of the field causing the error, first get the mapping:
 
-1. Check the mapping of your index:
+    ```console
+        GET your-index-name/_mapping
+    ```
 
-```console
-GET your-index-name/_mapping
-```
-
-2. Confirm the data type of the field causing the error.
-
-3. Ensure the incoming data matches the expected type.
-
-4. If necessary, create a new index with the correct mapping and reindex your data.
+Make sure the incoming data matches the expected type. If not, you'll need to fix the data or update the mapping. If necessary, create a new index with the correct mapping and reindex your data.

troubleshoot/elasticsearch/memory-locking-error.md

@@ -0,0 +1,60 @@
+---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
+navigation_title: "Error: token invalid or expired"
+---
+
+# Fix token invalid or expired error in Elasticsearch [token-invalid-expired]
+
+```console
+Error: token expired
+
+Error: invalid token
+```
+
+This error occurs when {{es}} receives a request containing an invalid or expired token during authentication. It's typically caused by missing, incorrect, or outdated tokens. If an invalid or expired token is used, {{es}} rejects the request.
+
+## Invalid token
+
+An invalid token will cause {{es}} to reject a request. Common causes include:
+
+- The token is expired or revoked
+- The token format is incorrect or malformed
+- The Authorization header is missing or doesn’t start with Bearer
+- The client or middleware failed to attach the token properly
+- Security settings in {{es}} are misconfigured
+
+To resolve this error:
+
+- Verify the token and ensure it's correctly formatted and current.
+- Check expiration and generate a new token if needed.
+- Inspect your client and confirm the token is sent in the `Authorization` header.
+- Review {{es}} settings and check that token auth is enabled:
+
+   ```yaml
+   xpack.security.authc.token.enabled: true
+   ```
+
+- Use logs for details: {{es}} logs may provide context about the failure.
+
+
+## Token expired
+
+This error occurs when {{es}} receives a request containing an expired token during authentication.
+
+To resolve this issue:
+
+- Refresh the token, and obtain a new token using your token refresh workflow.
+- Implement automatic token refresh and ensure your application is configured to refresh tokens before expiration.
+- Avoid using expired tokens and do not reuse tokens after logout or expiration.
+- Adjust token lifespan if needed and configure a longer token expiration in `elasticsearch.yml`, though this should be balanced against security needs:
+
+   ```yaml
+   xpack.security.authc.token.timeout: 20m
+   ```
+   

troubleshoot/elasticsearch/security/invalid-token.md

@@ -6,8 +6,7 @@ applies_to:
     ess: 
     ece: 
     self: 
-navigation_title: "Error: Unable to retrieve node fs stats"
-# is mapped_pages needed for newly created docs?
+navigation_title: "Error: unable to retrieve node fs stats"
 ---
 
 # Fix error: Unable to retrieve node fs stats [unable-to-retrieve-node-fs-stats]