Docs
  • Guides
  • APIs (opens in a new tab)
  • Products
    Elasticsearch Observability Security Elastic Cloud
  • Reference
  • Troubleshoot
  • Release notes
  1. Docs /
  2. Troubleshoot /
  3. Elasticsearch

Troubleshoot data issues in Elasticsearch

Use the topics in this section to troubleshoot data-related issues in your Elasticsearch deployments, including allocation problems, tiering issues, and shard limits.

  • Allow Elasticsearch to allocate the data in the system
  • Allow Elasticsearch to allocate the index
  • Add a preferred data tier to a deployment
  • Troubleshoot incomplete migration to data tiers
  • Warning: Not enough nodes to allocate all shard replicas
  • Total number of shards for an index on a single node exceeded
  • Total number of shards per node has been reached
  • Troubleshoot data corruption

Additional resources

  • Watermark errors
  • Troubleshooting overview
  • Contact us
Previous
Cluster allocation API examples
Next
Data allocation
  • View as Markdown
  • Report a docs issue
  • Edit this page
  • Learn how to contribute
Get started free
  • 14-day free trial
  • All features included
  • No setup required
On this page
  • Additional resources
Section
Troubleshoot
Docs Guides APIs (opens in a new tab) Reference Troubleshoot Release notes
Version
Troubleshoot
Elasticsearch
  • Overview
  • 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
    • Cluster allocation API examples
  • 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
    • Ingest Pipelines
    • Timestamp data quality
  • 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
  • File-based access recovery
  • Upgrades
  • Upgrade Assistant
  • Security
    • Nodes info API response
    • Authorization errors
    • Error: Extra arguments provided
    • Active Directory account lockout
    • 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
Elastic logo
  • Trademarks
  • Terms of Use
  • Privacy
  • Sitemap

© 2026 Elasticsearch B.V. All Rights Reserved.

This content is available in different formats for convenience only. All original licensing terms apply.

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.