0Pricing
Elasticsearch & Full Text Search Systems · Lesson

Shard Allocation and Rebalancing

Understand how Elasticsearch decides where shards live, how allocation awareness spreads replicas across hardware, and how to control rebalancing during scaling and maintenance.

Shard Allocation and Rebalancing is a free Elasticsearch & Full Text Search Systems lesson on CoddyKit — lesson 4 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Elasticsearch & Full Text Search Systems learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Where Do Shards Go?

When you create an index or add a node, Elasticsearch must decide which node holds each shard. This process is shard allocation, and keeping it balanced is key to a healthy, performant cluster.

The Allocation Process

The master node runs allocation deciders for every unassigned shard. They check disk space, shard count, awareness rules, and filters before placing a shard. Failing any decider keeps the shard UNASSIGNED.

Primary vs Replica Placement

A replica is never allocated to the same node as its primary. This guarantees that losing one node cannot take out both copies of the same data. With one replica you survive any single-node failure.

Watching Allocation

Use the _cat/shards API to see where each shard sits and its state. STARTED means active; RELOCATING means it is moving.

GET _cat/shards?v

Explaining a Stuck Shard

When a shard will not allocate, the _cluster/allocation/explain API tells you exactly which decider blocked it and why. This is the first stop for debugging a yellow or red cluster.

GET _cluster/allocation/explain
{
  "index": "my_index",
  "shard": 0,
  "primary": false
}

Allocation Awareness

Allocation awareness spreads copies across physical boundaries like racks or availability zones. You tag nodes with custom attributes and tell the cluster to be aware of them.

cluster.routing.allocation.awareness.attributes: zone

Forced Awareness

Forced awareness goes further: it refuses to over-allocate replicas to surviving zones if a zone goes down, preventing one zone from holding all copies. This protects capacity planning during outages.

cluster.routing.allocation.awareness.force.zone.values: zone1,zone2

Shard Filtering

You can pin or exclude an index from specific nodes using allocation filters. This is handy for hot/warm architectures where older indices migrate to cheaper hardware.

PUT my_index/_settings
{
  "index.routing.allocation.require.box_type": "warm"
}

Rebalancing

After nodes join or leave, the cluster rebalances to even out shard counts. This is automatic but generates network and disk I/O, so it should be controlled during sensitive operations.

Pausing Allocation

Before a rolling restart, disable allocation so the cluster does not waste effort relocating shards from a node you are about to bring back. Re-enable it afterward.

PUT _cluster/settings
{
  "transient": {
    "cluster.routing.allocation.enable": "primaries"
  }
}

Throttling

Limit concurrent recoveries with cluster.routing.allocation.node_concurrent_recoveries and bandwidth with indices.recovery.max_bytes_per_sec to keep rebalancing from starving live queries.

Quick Check

Test your understanding of shard allocation.

Recap

You learned how shards are placed and balanced:

  • Allocation deciders choose shard locations; replicas avoid their primary's node.
  • Debug stuck shards with allocation/explain.
  • Allocation awareness and forced awareness spread copies across zones.
  • Use allocation filters for hot/warm tiers and disable allocation during rolling restarts.

Frequently asked questions

Is the “Shard Allocation and Rebalancing” lesson free?

Yes — the full text of “Shard Allocation and Rebalancing” is free to read here on the web, and the Elasticsearch & Full Text Search Systems course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Elasticsearch & Full Text Search Systems course, upgrade to CoddyKit PRO.

What will I learn in “Shard Allocation and Rebalancing”?

Understand how Elasticsearch decides where shards live, how allocation awareness spreads replicas across hardware, and how to control rebalancing during scaling and maintenance. You practise Elasticsearch & Full Text Search Systems with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Elasticsearch & Full Text Search Systems?

No prior experience is required. Elasticsearch & Full Text Search Systems on CoddyKit is structured for beginners through advanced learners; this is — lesson 4 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Shard Allocation and Rebalancing” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Elasticsearch & Full Text Search Systems lesson?

Yes. Every Elasticsearch & Full Text Search Systems lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Sharding and Replicas Explained
  2. Cluster Health and Monitoring
  3. Node Roles and Architecture
  4. Shard Allocation and Rebalancing
← Back to Elasticsearch & Full Text Search Systems