# Index size not accurate

**URL:** <https://discuss.elastic.co/t/index-size-not-accurate/73356>\
**Category:** Elasticsearch\
**Created:** [January 31, 2017, 12:00pm UTC](https://discuss.elastic.co/t/index-size-not-accurate/73356 "2017-01-31T12:00:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwjvaughan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dwjvaughan/32/10648_2.png) [@dwjvaughan](https://discuss.elastic.co/u/dwjvaughan)\
**Post date:** [January 31, 2017, 12:00pm UTC](https://discuss.elastic.co/t/index-size-not-accurate/73356/1 "2017-01-31T12:00:27Z")

</div>

I have a single node 5.1.2 cluster with a filebeat index on. I'm seeing some pretty big differences with the size reported by Elasticsearch and size on disk. E.g.

```
curl localhost:9200/_cat/indices/filebeat-2017.01.31?v

health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open filebeat-2017.01.31 KQSgom68Qqio4-KOAwW-UQ 5 0 3082004 0 890.3mb 890.3mb

```

But on the OS:

```
du -hs nodes/0/indices/KQSgom68Qqio4-KOAwW-UQ
3.3G nodes/0/indices/KQSgom68Qqio4-KOAwW-UQ

```

Am I missing something here?

EDIT: Wait... I think I just figured it out, it's the translog.

---

<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 28, 2017, 12:00pm UTC](https://discuss.elastic.co/t/index-size-not-accurate/73356/2 "2017-02-28T12:00:33Z")

</div>

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