# ES 2.1.1 translog grows forever

**URL:** <https://discuss.elastic.co/t/es-2-1-1-translog-grows-forever/42569>\
**Category:** Elasticsearch\
**Created:** [February 24, 2016, 9:24am UTC](https://discuss.elastic.co/t/es-2-1-1-translog-grows-forever/42569 "2016-02-24T09:24:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\
**Post date:** [February 24, 2016, 9:24am UTC](https://discuss.elastic.co/t/es-2-1-1-translog-grows-forever/42569/1 "2016-02-24T09:24:03Z")

</div>

We are performing many writes and updates in our ES 2.1.1 cluster, and within ~2 weeks time the translog reaches 50GB on disk, and continues to grow seemingly indefinitely.

Is this a known issue? was it fixed in newer versions? can this be fixed on 2.1.1 without upgrading to a newer version for now?

Thanks

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [February 25, 2016, 4:24am UTC](https://discuss.elastic.co/t/es-2-1-1-translog-grows-forever/42569/2 "2016-02-25T04:24:24Z")

</div>

Yes, this is a [known bug](https://github.com/elastic/elasticsearch/pull/15830) fixed in 2.1.2 and 2.2.0. You can issue flush commands to clear and thus workaround until you can upgrade.

---

<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:** [July 5, 2017, 11:13pm UTC](https://discuss.elastic.co/t/es-2-1-1-translog-grows-forever/42569/3 "2017-07-05T23:13:48Z")

</div>