Elasticsearch Limit of Total Fields [1000] Exceeded

How to fix it

Try these in order — the most common fix is first.

1. 1. Contain the damage

   Copy steps
   1. Set index.mapping.total_fields.ignore_dynamic_beyond_limit to true to ignore new dynamic fields instead of rejecting documents
   2. Raise the limit cautiously: Elastic says 10000 is usually fine, 100000 has strong performance implications
   Did this fix it? Yes No

2. 2. Fix the mapping

   Copy steps
   1. Use the flattened type for large arbitrary key sets and runtime fields to query them
   2. Disable dynamic mapping in the index template for future indices
   3. Reindex into an index with a corrected mapping
   Did this fix it? Yes No

3. 3. Count and find fields

   Copy steps
   1. Use GET <index>/_mapping or the field capabilities API with fields=*
   2. Use analyze index disk usage to spot unused fields
   Did this fix it? Yes No

Symptoms

Indexing fails with 'Limit of total fields [1000] in index has been exceeded'; high heap or CPU, slow Kibana Discover field loading.

Why it happens

• Dynamic mapping on arbitrary or user-generated keys
• Upstream formatting bug producing new field names
• Many indices combined in one data view

This guide also covers

• elasticsearch limit of total fields exceeded
• elasticsearch mapping explosion
• elasticsearch total_fields.limit

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Algolia Record Quota Exceeded or Limit Reached (Algolia)

Other Elasticsearch errors

• Elasticsearch Cluster Health Yellow: Causes and Fixes
• Elasticsearch Cluster Health Red: How to Fix It
• Elasticsearch Unassigned Shards: Why and How to Fix
• Elasticsearch circuit_breaking_exception: Data Too Large
• Elasticsearch High JVM Memory Pressure and Out of Memory
• Elasticsearch Disk Watermark: Index Read-Only (FORBIDDEN/12)
• Why Is Elasticsearch So Slow? Fixing Slow Searches
• Elasticsearch Cannot Change Field Mapping: Reindex Guide