# ES 2.1.2 not\_analyzed string fields default doc\_values enabled, but ES get OOM when using cardinality

**URL:** <https://discuss.elastic.co/t/es-2-1-2-not-analyzed-string-fields-default-doc-values-enabled-but-es-get-oom-when-using-cardinality/85366>\
**Category:** Elasticsearch\
**Created:** [May 11, 2017, 10:03am UTC](https://discuss.elastic.co/t/es-2-1-2-not-analyzed-string-fields-default-doc-values-enabled-but-es-get-oom-when-using-cardinality/85366 "2017-05-11T10:03:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zous](https://avatars.discourse-cdn.com/v4/letter/z/b3f665/32.png) [@zous](https://discuss.elastic.co/u/zous)\
**Post date:** [May 11, 2017, 10:03am UTC](https://discuss.elastic.co/t/es-2-1-2-not-analyzed-string-fields-default-doc-values-enabled-but-es-get-oom-when-using-cardinality/85366/1 "2017-05-11T10:03:14Z")

</div>

We are using elaseticsearch 2.1.2, and some string fields not\_analyzed, when using cardinality, elasticsearch got OOM, doc\_values is enabled by default, why elasticsearch still get OOM, it's supposed to consume memory from file system cache indstead of ES java heap, any advice?

---

<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:** [June 8, 2017, 10:07am UTC](https://discuss.elastic.co/t/es-2-1-2-not-analyzed-string-fields-default-doc-values-enabled-but-es-get-oom-when-using-cardinality/85366/2 "2017-06-08T10:07:26Z")

</div>

Closed on June 8, 2017, 10:07am UTC

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