# Spike in Fielddata memory usage
**URL:** https://discuss.elastic.co/t/spike-in-fielddata-memory-usage/183065
**Category:** Elasticsearch
**Created:** [May 28, 2019, 10:42am UTC](https://discuss.elastic.co/t/spike-in-fielddata-memory-usage/183065 "2019-05-28T10:42:28Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@prbhardwaj](https://discuss.elastic.co/u/prbhardwaj)
#### Post date: [May 28, 2019, 10:42am UTC](https://discuss.elastic.co/t/spike-in-fielddata-memory-usage/183065/1 "2019-05-28T10:42:28Z")
ES Version: 5.5.1
We use Elasticsearch mainly for term aggregation. In one of our index, we see a spike in field data memory usage which corresponds with a spike in CPU utilization and load average too. All the fields in that index are either keyword, integer or float. From reading the documentation I know that only 'text' fields use field data for sorting and aggregation. Since we do not have any text field in our index then why there is a spike in field data memory usage. Also, we haven't set `indices.fielddata.cache.size` so cache is unbounded, there is no eviction from field data.
Any pointer in understanding this will be quite helpful.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 25, 2019, 10:42am UTC](https://discuss.elastic.co/t/spike-in-fielddata-memory-usage/183065/2 "2019-06-25T10:42:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.