# Slowed down query and high fielddata evictions

**URL:** <https://discuss.elastic.co/t/slowed-down-query-and-high-fielddata-evictions/72556>\
**Category:** Elasticsearch\
**Created:** [January 24, 2017, 3:02am UTC](https://discuss.elastic.co/t/slowed-down-query-and-high-fielddata-evictions/72556 "2017-01-24T03:02:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![suanmeiguo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/suanmeiguo/32/11758_2.png) [@suanmeiguo](https://discuss.elastic.co/u/suanmeiguo)\
**Post date:** [January 24, 2017, 3:02am UTC](https://discuss.elastic.co/t/slowed-down-query-and-high-fielddata-evictions/72556/1 "2017-01-24T03:02:26Z")

</div>

I have an Elasticsearch cluster with about 10 slaves nodes. Nodes are c4.xlarge (16 core and 32G ram). When run a term aggregation query (it's actually aggregates on an analyzed field), it takes about 2 minutes to get result back and I see there are a lot of fielddata eviction. Usually the query finishes in less than 10 seconds.

I have following config in my both cluster:

```auto
indices.fielddata.cache.size: 50%
indices.breaker.fielddata.limit: 70%
indices.breaker.request.limit: 30%

```

Is there any direction or clue I can look for? I don't really have a good idea to debug this. I know fielddata is used for filter but no more than that. Any tip will help. Appreciate it!

---

<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 21, 2017, 3:02am UTC](https://discuss.elastic.co/t/slowed-down-query-and-high-fielddata-evictions/72556/2 "2017-02-21T03:02:26Z")

</div>

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