Skip to content

Commit 61dd0ae

Browse files
committed
updates
1 parent 1af32b5 commit 61dd0ae

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

deploy-manage/distributed-architecture.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ applies_to:
2323
The topics in this section provides information about the architecture of {{es}} and how it stores and retrieves data:
2424

2525
::::{note}
26-
{{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}}.
26+
{{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}}. Instead, the information in this section will provide you information about how the platform works for you.
2727
::::
2828

2929
* [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.
@@ -33,4 +33,5 @@ The topics in this section provides information about the architecture of {{es}}
3333
* [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.
3434
* [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.
3535
* [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.
36+
* [Kibana task management](distributed-architecture/kibana-tasks-management.md): Learn how {{kib}} runs background tasks and distribute work across multiple {{kib}} instances to be persistent and scale with your deployment.
3637

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

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
---
22
mapped_pages:
33
- https://www.elastic.co/guide/en/elasticsearch/reference/current/nodes-shards.html
4+
applies_to:
5+
stack:
6+
serverless:
47
---
58

69
# Clusters, nodes, and shards [nodes-shards]
@@ -14,7 +17,6 @@ Nodes and shards are what make {{es}} distributed and scalable. These concepts a
1417

1518
::::
1619

17-
1820
You can add servers (*nodes*) to a cluster to increase capacity, and {{es}} automatically distributes your data and query load across all of the available nodes.
1921

2022
Elastic is able to distribute your data across nodes by subdividing an index into *shards*. Each index in {{es}} is a grouping of one or more physical shards, where each shard is a self-contained Lucene index containing a subset of the documents in the index. By distributing the documents in an index across multiple shards, and distributing those shards across multiple nodes, {{es}} increases indexing and query capacity.
@@ -23,7 +25,6 @@ There are two types of shards: *primaries* and *replicas*. Each document in an i
2325

2426
::::{tip}
2527
The number of primary shards in an index is fixed at the time that an index is created, but the number of replica shards can be changed at any time, without interrupting indexing or query operations.
26-
2728
::::
2829

2930
Shard copies in your cluster are automatically balanced across nodes to provide scale and high availability. All nodes are aware of all the other nodes in the cluster and can forward client requests to the appropriate node. This allows {{es}} to distribute indexing and query load across the cluster.

0 commit comments

Comments
 (0)