# Elastic Mapping explosion **URL:** \ **Category:** Elasticsearch\ **Created:** [January 2, 2019, 12:03pm UTC](https://discuss.elastic.co/t/elastic-mapping-explosion/162647 "2019-01-02T12:03:08Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\ **Post date:** [January 8, 2019, 10:00am UTC](https://discuss.elastic.co/t/elastic-mapping-explosion/162647/11 "2019-01-08T10:00:25Z")
We may be talking at cross-purposes. I don't think of "a mapping explosion" as a specific error or event. I think of it as a general condition of having a lot of fields. It's a condition that can lead to a number of problems (memory pressure, delays publishing cluster state..) and is the reason we introduced a soft-limit to the number of fields in mappings. > If there are 2000 fields in my mapping file but the number of documents I am indexing is low (50,000). Sounds like a lot of fields for users to consider/search but shouldn't be too much of a problem. --- _[View the full topic](https://discuss.elastic.co/t/elastic-mapping-explosion/162647)._