# Elasticsearch falsely(?) reporting it has reached the field limit **URL:** \ **Category:** Elasticsearch\ **Created:** [September 25, 2023, 5:27pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794 "2023-09-25T17:27:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![dpitchford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpitchford/32/113171_2.png) [@dpitchford](https://discuss.elastic.co/u/dpitchford)\ **Post date:** [September 25, 2023, 5:27pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794/1 "2023-09-25T17:27:51Z")
When trying to index documents into an Elasticsearch 6.8.22 instance, I am seeing error messages like this: `{'index': {'_index': 'data_explorer', '_type': 'flywheel', '_id': '64ff3d667ed067064bf7bd7e', 'status': 400, 'error': {'type': 'illegal_argument_exception', 'reason': 'Limit of total fields [15000] in index [data_explorer] has been exceeded'}}, 'partition_id': 'jey3j3sDdrQV', 'shard_id': None, 'path': {'group': 'parker', 'project': '64ff3b877ed067064bf7bd1b'}}` However, if I hit the `/data_explorer` endpoint to get information about this index, I see that it has fewer than 11500 total fields. Why is it reporting that it has reached the 15000 field limit when it has fewer than 11500 fields? Is my process for checking the index information missing some fields? ---
**Author:** ![coezdemir](https://avatars.discourse-cdn.com/v4/letter/c/7c8e57/32.png) [@coezdemir](https://discuss.elastic.co/u/coezdemir)\ **Post date:** [September 26, 2023, 2:32pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794/2 "2023-09-26T14:32:55Z")
Hello welcome, This is a very old version of elastic, first recommendation is to update it. With that said, the mapping types are depreceated and also they are removed with Elasticsearch 8.x. I have a suspicion that if you get the mappings for /data\_explorer/\_mapping/flywheel instead of just /data\_explorer you will see there are more mappings and thus more fields on the index. Could you please try that? ---
**Author:** ![dpitchford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpitchford/32/113171_2.png) [@dpitchford](https://discuss.elastic.co/u/dpitchford)\ **Post date:** [September 26, 2023, 3:10pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794/3 "2023-09-26T15:10:46Z")
We are planning to upgrade to ES 7 in the next few months, and 8 at some point after that. Nonetheless, this behavior isn't a known issue with ES 6.8.22, is it? I tried the `/data_explorer/_mapping/flywheel` endpoint as you suggested. The resulting JSON is slightly different, but I still see the exact same number of fields. Do [multi-fields](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/multi-fields.html) count as multiple fields toward the field limit? ---
**Author:** ![dpitchford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dpitchford/32/113171_2.png) [@dpitchford](https://discuss.elastic.co/u/dpitchford)\ **Post date:** [October 17, 2023, 5:26pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794/4 "2023-10-17T17:26:45Z")
Answer: multi-fields **do** count toward the field limit. That, combined with some miscounting on my part, accounts for the strange behavior I was seeing. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 14, 2023, 5:27pm UTC](https://discuss.elastic.co/t/elasticsearch-falsely-reporting-it-has-reached-the-field-limit/343794/5 "2023-11-14T17:27:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.