﻿---
title: Clusters, nodes, and shards
description: You can add servers (nodes) to a cluster to increase capacity, and Elasticsearch automatically distributes your data and query load across all of the...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5568/deploy-manage/distributed-architecture/clusters-nodes-shards
products:
  - Elasticsearch
applies_to:
  - Elastic Stack: Generally available
---

# Clusters, nodes, and shards
<note>
  Nodes and shards are what make Elasticsearch distributed and scalable. These concepts aren’t essential if you’re just getting started. How you [deploy Elasticsearch](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5568/get-started/deployment-options) in production determines what you need to know:
  - **Self-managed Elasticsearch**: You are responsible for setting up and managing clusters, nodes, shards, and replicas. This includes managing the underlying infrastructure, scaling, and ensuring high availability through failover and backup strategies.
  - **Managed deployments**: This includes deployments on ECH, ECE, and ECK. Elastic can autoscale resources in response to workload changes. Choose from different deployment types to apply sensible defaults for your use case. A basic understanding of nodes, shards, and replicas is still important.
  - **Elastic Cloud Serverless**: You don’t need to worry about nodes, shards, or replicas. These resources are 100% automated on the serverless platform, which is designed to scale with your workload.
</note>

You can add servers (*nodes*) to a cluster to increase capacity, and Elasticsearch automatically distributes your data and query load across all of the available nodes.
Elastic is able to distribute your data across nodes by subdividing an index into *shards*. Each index in Elasticsearch 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, Elasticsearch increases indexing and query capacity.
There are two types of shards: *primaries* and *replicas*. Each document in an index belongs to one primary shard. A replica shard is a copy of a primary shard. Replicas maintain redundant copies of your data across the nodes in your cluster. This protects against hardware failure and increases capacity to serve read requests like searching or retrieving a document.
<tip>
  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.
</tip>

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 Elasticsearch to distribute indexing and query load across the cluster.
If you’re exploring Elasticsearch for the first time or working in a development environment, then you can use a cluster with a single node and create indices with only one shard. However, in a production environment, you should build a cluster with multiple nodes and indices with multiple shards to increase performance and resilience.
- To learn about optimizing the number and size of shards in your cluster, refer to [Size your shards](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5568/deploy-manage/production-guidance/optimize-performance/size-shards).
- To learn about how read and write operations are replicated across shards and shard copies, refer to [Reading and writing documents](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5568/deploy-manage/distributed-architecture/reading-and-writing-documents).
- To adjust how shards are allocated and balanced across nodes, refer to [Shard allocation, relocation, and recovery](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5568/deploy-manage/distributed-architecture/shard-allocation-relocation-recovery).