Observability Guides
EspañolEnglish
← Back to guidesGuide

Diagnose hot shards in OpenSearch before latency and indexing queues spiral

A practical guide to confirm real shard skew, separate symptoms from causes, and apply mitigations that do not make the cluster worse.

Learn how to confirm an OpenSearch hot shard, find the affected index and node, fix the actual cause, and validate that recovery is real.

Created: April 27, 2026

Published: April 27, 2026

Estimated time40 min
LevelAdvanced
Before you startAccess to the OpenSearch API or Dev Tools
PlatformsLinux / Docker
WhatsAppXLinkedIn

Docker

Useful when the cluster lives in containers and the simplest path is from the local node.

dockerReachable OpenSearch containercurl inside or outside the container
Inspect shards from the container
docker exec opensearch-node1 curl -s http://localhost:9200/_cat/shards/logs-prod-*?v&s=store:desc
Check allocation and disk usage
docker exec opensearch-node1 curl -s http://localhost:9200/_cat/allocation?v&s=disk.percent:desc
Also available inDiagnosticar hot shards en OpenSearch antes de que se disparen la latencia y las colas de indexación

Content locked

This guide requires both steps before full content is available.

  • ○Click “Like” on this guide.
  • ○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.