# Reason behind Mapping Explosion in Elasticsearch

**URL:** <https://discuss.elastic.co/t/reason-behind-mapping-explosion-in-elasticsearch/164150>\
**Category:** Elasticsearch\
**Created:** [January 14, 2019, 2:03pm UTC](https://discuss.elastic.co/t/reason-behind-mapping-explosion-in-elasticsearch/164150 "2019-01-14T14:03:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pranav24](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@pranav24](https://discuss.elastic.co/u/pranav24)\
**Post date:** [January 14, 2019, 2:03pm UTC](https://discuss.elastic.co/t/reason-behind-mapping-explosion-in-elasticsearch/164150/1 "2019-01-14T14:03:31Z")

</div>

What actually leads to mapping explosion? With 32 GB RAM and over 2000 fields why Elastic needs that much memory that it can lead to mapping explosion. What relationship with memory this number of fields has which leads to such kinds of OOM and crashes even on systems with healthy RAM

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 11, 2019, 2:03pm UTC](https://discuss.elastic.co/t/reason-behind-mapping-explosion-in-elasticsearch/164150/2 "2019-02-11T14:03:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.