Docs
  • Release notes
  • Troubleshoot
  • Reference
  • Get started
  • Solutions and use cases
  • Manage data
  • Explore and analyze
  • Deploy and manage
  • Manage your Cloud account and preferences
  • Extend and contribute
  • Release notes
  • Reference
  • Elasticsearch
    • Clusters
      • Common cluster issues
        • Watermark errors
        • Circuit breaker errors
        • High CPU usage
        • High JVM memory pressure
        • Red or yellow health status
        • Rejected requests
        • Task queue backlog
        • Mapping explosion
        • Hot spotting
      • Unstable clusters
      • Unbalanced clusters
      • Remote clusters
      • Unassigned shards
      • Shard capacity issues
    • Data
      • Data allocation
      • Index allocation
      • Preferred data tier
      • Incomplete migration to data tiers
      • Not enough nodes to allocate shard replicas
      • Total number of shards for an index exceeded
      • Total number of shards per node reached
      • Data corruption
    • Capacity
      • Data nodes out of disk
        • Increase disk capacity
        • Decrease disk usage
      • Master nodes out of disk
      • Other nodes out of disk
    • Snapshot and restore
      • Restore from snapshot
      • Broken repositories
        • Corrupted repositories
        • Unknown repositories
        • Invalid repositories
      • Snapshot policy failures
    • Searches
    • Lifecycle management
    • Index lifecycle management errors
    • Security
      • Nodes info API response
      • Authorization errors
      • Error: Extra arguments provided
      • Active Directory
      • Certificate verification with curl on Mac
      • SSLHandshakeException
      • SSL/TLS exceptions
      • Kerberos
      • SAML
      • Kibana internal server error
      • Password setup failures
      • Configuration file locations
      • Error: Token invalid or expired
    • Error reference
      • Error: All shards failed
      • Error: Failed to parse field of type in document with id
      • Error: Unable to retrieve node fs stats
      • Error: Unable to parse response body
    • Clients
    • Diagnostics
    • More topics
      • Discovery
      • Monitoring
      • Transforms
      • Watcher
      • Apache Hadoop
  • Kibana
    • Server logs
    • Server status
    • Error: Server not ready
    • Trace Elasticsearch query
    • Monitoring
    • Alerts
    • Reporting
    • Task Manager
    • Maps
    • Graph
    • Migration and upgrades
    • Diagnostics
  • Observability
    • Explore data
    • Inspect
    • Synthetics
    • Uptime
    • Logs
    • APM
      • Common problems
      • APM Server or Elasticsearch is down
      • APM Server response codes
      • Processing and performance
      • APM Server binary debugging
      • APM Server performance diagnostic
      • APM Go Agent
      • APM iOS Agent
      • APM Java Agent
      • APM .NET agent
      • APM Node.js Agent
      • APM PHP Agent
        • Agent is not instrumenting code
        • Collection of diagnostic information
      • APM Python Agent
      • APM Ruby Agent
      • APM Real User Monitoring JavaScript Agent
    • Amazon Data Firehose
    • Universal Profiling
      • Troubleshoot the backend
    • Infrastructure monitoring
      • Understand "no results found" message
    • SLOs
  • Security
    • Detection rules
    • Elastic Defend
    • Indicators of compromise
    • Agentless integrations FAQ
  • Ingest tools
    • Logstash
      • Plugins
        • Kafka
        • Azure Event Hub
      • Health report pipelines
      • Contribute and discuss
    • Fleet and Elastic Agent
      • Common problems
      • Frequently asked questions
    • Elastic Logging Plugin for Docker
    • Elastic Serverless Forwarder
  • Elastic Cloud
    • Serverless status
    • SAML single sign-on (SSO)
    • Unavailable nodes
    • Unavailable shards
    • Performance
      • High memory pressure
      • Cluster performance metrics
      • Cluster response time
    • Node moves and outages
    • Deployment health warnings
    • Node bootlooping
  • Elastic Cloud Enterprise
    • Common issues
    • Emergency roles token
    • Removing containers
    • Container engines
    • ZooKeeper sync status
    • Zookeeper quorum
    • Deployment health warnings
    • Node bootlooping
    • Diagnostics
    • Heap dumps
    • Thread dumps
  • Elastic Cloud on Kubernetes
    • Common issues
    • Resources and logs
    • Diagnostics
    • JVM heap dumps
Loading
  1. Docs
  2. / Troubleshoot
  3. / Elasticsearch
  4. /

Troubleshoot Elasticsearch clusters

Use the topics in this section to troubleshoot Elasticsearch clusters.

  • Fix common cluster issues
  • Troubleshoot an unstable cluster
  • Troubleshoot an unbalanced cluster
  • Troubleshoot remote clusters
  • Diagnose unassigned shards
  • Troubleshoot shard capacity health issues

Additional resources

  • Troubleshooting overview
  • Contact us
Previous
Elasticsearch
Next
Common cluster issues
  • Current version ✓
  • Previous version
  • Edit this page
  • Report an issue
On this page
  • Additional resources
Elastic logo
  • Trademarks
  • Terms of Use
  • Privacy
  • Sitemap

© 2025 Elasticsearch B.V. All Rights Reserved.

Elasticsearch is a trademark of Elasticsearch B.V., registered in the U.S. and in other countries. Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Welcome to the docs for the latest Elastic product versions, including Elastic Stack 9.0 and Elastic Cloud Serverless. To view previous versions, go to elastic.co/guide.