Skip to content

Commit 1553509

Browse files
committed
further updateS
1 parent a78fa6d commit 1553509

File tree

11 files changed

+27
-14
lines changed

11 files changed

+27
-14
lines changed

deploy-manage/distributed-architecture.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,15 @@ mapped_pages:
1919

2020
The topics in this section provides information about the architecture of {{es}} and how it stores and retrieves data:
2121

22-
* [Nodes and shards](distributed-architecture/clusters-nodes-shards.md): Learn about the basic building blocks of an {{es}} cluster, including nodes, shards, primaries, and replicas.
23-
* [Node roles](distributed-architecture/clusters-nodes-shards/node-roles.md): Learn about the different roles that nodes can have in an {{es}} cluster.
22+
::::{note}
23+
{{serverless-full}} scales with your workload and automates nodes, shards, and replicas for you. Some of the content in this section does not apply to you if you are using {{serverless-full}}.
24+
::::
25+
26+
* [Cluster, nodes, and shards](distributed-architecture/clusters-nodes-shards.md): Learn about the basic building blocks of an {{es}} cluster, including nodes, shards, primaries, and replicas.
27+
* [Node roles](distributed-architecture/clusters-nodes-shards/node-roles.md): Learn about the different roles that nodes can have in an {{es}} cluster.
2428
* [Reading and writing documents](distributed-architecture/reading-and-writing-documents.md): Learn how {{es}} replicates read and write operations across shards and shard copies.
2529
* [Shard allocation, relocation, and recovery](distributed-architecture/shard-allocation-relocation-recovery.md): Learn how {{es}} allocates and balances shards across nodes.
2630
* [Shard allocation awareness](distributed-architecture/shard-allocation-relocation-recovery/shard-allocation-awareness.md): Learn how to use custom node attributes to distribute shards across different racks or availability zones.
31+
* [Disocvery and cluster formation](distributed-architecture/discovery-cluster-formation.md): Learn about the cluster formation process including voting, adding nodes and publishing the cluster state.
2732
* [Shard request cache](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/shard-request-cache-settings.md): Learn how {{es}} caches search requests to improve performance.
2833

deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ Any time that you start an instance of {{es}}, you are starting a *node*. A coll
99

1010
Each node performs one or more roles. Roles control the behavior of the node in the cluster.
1111

12-
1312
## Set node roles [set-node-roles]
1413

1514
You define a node’s roles by setting `node.roles` in [`elasticsearch.yml`](../../deploy/self-managed/configure-elasticsearch.md). If you set `node.roles`, the node is only assigned the roles you specify. If you don’t set `node.roles`, the node is assigned the following roles:
@@ -30,10 +29,7 @@ You define a node’s roles by setting `node.roles` in [`elasticsearch.yml`](../
3029
If you set `node.roles`, ensure you specify every node role your cluster needs. Every cluster requires the following node roles:
3130

3231
* `master`
33-
*
34-
35-
`data_content` and `data_hot`<br> OR<br> `data`
36-
32+
* `data_content` and `data_hot`<br> OR<br> `data`
3733

3834
Some {{stack}} features also require specific node roles:
3935

deploy-manage/distributed-architecture/discovery-cluster-formation.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery.html
4+
applies_to:
5+
stack:
46
---
57

68
# Discovery and cluster formation [modules-discovery]

deploy-manage/distributed-architecture/discovery-cluster-formation/cluster-fault-detection.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-fault-detection.html
4+
applies_to:
5+
stack:
46
---
57

68
# Cluster fault detection [cluster-fault-detection]

deploy-manage/distributed-architecture/discovery-cluster-formation/cluster-state-overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-state-overview.html
4+
applies_to:
5+
stack:
46
---
57

68
# Cluster state [cluster-state-overview]

deploy-manage/distributed-architecture/discovery-cluster-formation/discovery-hosts-providers.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-hosts-providers.html
4+
applies_to:
5+
stack:
46
---
57

68
# Discovery [discovery-hosts-providers]

deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-bootstrap-cluster.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html
4+
applies_to:
5+
stack:
46
---
57

68
# Bootstrapping a cluster [modules-discovery-bootstrap-cluster]

deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-quorums.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-quorums.html
4+
applies_to:
5+
stack:
46
---
57

68
# Quorum-based decision making [modules-discovery-quorums]

deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-voting.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-voting.html
4+
applies_to:
5+
stack:
46
---
57

68
# Voting configurations [modules-discovery-voting]

deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/index-level-shard-allocation.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ The documentation team is working to combine content pulled from the following p
2828
* [/raw-migrated-files/elasticsearch/elasticsearch-reference/shard-allocation-filtering.md](../../../raw-migrated-files/elasticsearch/elasticsearch-reference/shard-allocation-filtering.md)
2929
* [/raw-migrated-files/elasticsearch/elasticsearch-reference/recovery-prioritization.md](../../../raw-migrated-files/elasticsearch/elasticsearch-reference/recovery-prioritization.md)
3030

31-
This module provides per-index settings to control the allocation of shards to nodes:
31+
In Elasticsearch, per-index settings allow you to control the allocation of shards to nodes through index-level shard allocation settings. These settings enable you to specify preferences or constraints for where shards of a particular index should reside. This includes allocating shards to nodes with specific attributes or avoiding certain nodes. This level of control helps optimize resource utilization, balance load, and ensure data redundancy and availability according to your deployment's specific requirements. In addition to the content in this article, there are additional resources:
3232

3333
* [Shard allocation filtering](../../../deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/index-level-shard-allocation.md): Controlling which shards are allocated to which nodes.
3434
* [Delayed allocation](../../../deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/delaying-allocation-when-node-leaves.md): Delaying allocation of unassigned shards caused by a node leaving.
@@ -87,9 +87,7 @@ To filter based on a custom node attribute:
8787
}
8888
```
8989

90-
91-
92-
### Index allocation filter settings [index-allocation-settings]
90+
### Index allocation filter settings [index-allocation-settings]
9391

9492
`index.routing.allocation.include.{{attribute}}`
9593
: Assign the index to a node whose `{{attribute}}` has at least one of the comma-separated values.
@@ -127,7 +125,6 @@ The index allocation settings support the following built-in attributes:
127125
`_tier` filtering is based on [node](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch/configuration-reference/node-settings.md) roles. Only a subset of roles are [data tier](../../../manage-data/lifecycle/data-tiers.md) roles, and the generic [data role](../../../deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#data-node-role) will match any tier filtering.
128126
::::
129127

130-
131128
You can use wildcards when specifying attribute values, for example:
132129

133130
```console
@@ -183,5 +180,4 @@ PUT index_4/_settings
183180
{
184181
"index.priority": 1
185182
}
186-
```
187-
183+
```

0 commit comments

Comments
 (0)