Skip to content

Commit e1c831e

Browse files
committed
Another batch
1 parent 7459bc5 commit e1c831e

File tree

9 files changed

+19
-12
lines changed

9 files changed

+19
-12
lines changed

troubleshoot/elasticsearch/add-tier.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,14 @@
11
---
2-
navigation_title: Add a missing tier
2+
navigation_title: Index allocation data tier
33
mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/add-tier.html
55
---
66

7-
# Add a missing tier to the system [add-tier]
7+
% marciw move this page to a new index allocation subsection
8+
% or just move it down in the ToC
9+
% and this page really really needs rewriting
10+
11+
# Add a preferred data tier to a deployment [add-tier]
812

913
The allocation of indices in an {{es}} deployment can be allocated on [data tiers](../../manage-data/lifecycle/data-tiers.md).
1014

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
navigation_title: Allow data allocation
2+
navigation_title: Data allocation
33
mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-cluster-allocation.html
55
---

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
navigation_title: Allow index allocation
2+
navigation_title: Index allocation
33
mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-index-allocation.html
55
---

troubleshoot/elasticsearch/diagnose-unassigned-shards.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
navigation_title: Unassigned shards
23
mapped_pages:
34
- https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnose-unassigned-shards.html
45
---

troubleshoot/elasticsearch/elasticsearch-reference/security.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,12 @@
11
---
2-
navigation_title: "Troubleshooting"
2+
navigation_title: "Security"
33
mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/security-troubleshooting.html
55
---
66

7+
% marciw: this page needs to move to the security folder
78

8-
9-
# Security [security-troubleshooting]
10-
9+
# Troubleshoot {{es}} security [security-troubleshooting]
1110

1211
Use the information in this section to troubleshoot common problems and find answers for frequently asked questions.
1312

troubleshoot/elasticsearch/fix-common-cluster-issues.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,5 @@
11
---
2+
navigation_title: Common cluster issues
23
mapped_pages:
34
- https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-common-cluster-issues.html
45
---

troubleshoot/elasticsearch/increase-tier-capacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-tier-capacity.html
44
---
55

6-
# Not enough nodes to allocate all shard replicas [increase-tier-capacity]
6+
# Warning: Not enough nodes to allocate all shard replicas [increase-tier-capacity]
77

88
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.
99

troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
---
2-
navigation_title: Mix of data tiers and node roles
2+
navigation_title: Incomplete migration to data tiers
33
mapped_pages:
44
- https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshoot-migrate-to-tiers.html
55
---
66

7-
# Mix of index allocation filters and data tier node roles [troubleshoot-migrate-to-tiers]
7+
% old title: Mix of index allocation filters and data tier node roles
8+
9+
# Troubleshoot incomplete migration to data tiers [troubleshoot-migrate-to-tiers]
810

911
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.
1012

troubleshoot/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ toc:
1515
- file: elasticsearch/mapping-explosion.md
1616
- file: elasticsearch/hotspotting.md
1717
- file: elasticsearch/diagnose-unassigned-shards.md
18-
- file: elasticsearch/add-tier.md
1918
- file: elasticsearch/allow-all-cluster-allocation.md
2019
- file: elasticsearch/allow-all-index-allocation.md
20+
- file: elasticsearch/add-tier.md
2121
- file: elasticsearch/troubleshoot-migrate-to-tiers.md
2222
- file: elasticsearch/increase-tier-capacity.md
2323
- file: elasticsearch/increase-shard-limit.md

0 commit comments

Comments
 (0)