# Data too large for tiny index in Kibana
**URL:** https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694
**Category:** Elasticsearch
**Created:** [March 29, 2016, 1:57pm UTC](https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694 "2016-03-29T13:57:54Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@steinmr](https://discuss.elastic.co/u/steinmr)
#### Post date: [March 29, 2016, 1:57pm UTC](https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694/1 "2016-03-29T13:57:54Z")
I have a tiny index (400kB) that I try to do "Discover" on in Kibana. It gives me the error:
Data too large, data for [TimestampUtc] would be larger than limit of [2508954009/2.3gb]]
How can this be? I'm currently increasing the cluster size to overcome this, but there seems to be no reason to use over 2,3gb to store 800 documents...
Cluster 376b3a
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [March 29, 2016, 8:53pm UTC](https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694/2 "2016-03-29T20:53:45Z")
It probably means fielddata, is that field analysed in your mappings?
---
### Author:  [@steinmr](https://discuss.elastic.co/u/steinmr)
#### Post date: [March 30, 2016, 7:11am UTC](https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694/3 "2016-03-30T07:11:17Z")
Thank you for your answer.
No, it is just a date field, not analyzed:
"TimestampUtc": {
"type": "date",
"format": "epoch\_millis||dateOptionalTime"
},
But even if it was, 400kb of data could not fill 2,3gb?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:04pm UTC](https://discuss.elastic.co/t/data-too-large-for-tiny-index-in-kibana/45694/4 "2017-07-05T23:04:09Z")