# HUGE Transaction Log **URL:** \ **Category:** Elasticsearch\ **Created:** [February 7, 2017, 6:23pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261 "2017-02-07T18:23:19Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![rellimcire](https://avatars.discourse-cdn.com/v4/letter/r/c67d28/32.png) [@rellimcire](https://discuss.elastic.co/u/rellimcire)\ **Post date:** [February 7, 2017, 6:23pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/1 "2017-02-07T18:23:19Z")
I'm running ES 2.0.0. During a 48 hour test I have transaction logs that are almost 60Gb and growing. It seems to not be flushing. I could try a manual flush but don't understand why I would need to do that. My understanding is flushing happens automatically whenever the translog is too big (default 512Mb) or after 30 minutes. We're running a single node. Our index is named "report" I see five folders in esearch/data/iTE/nodes/0/indices/report. ``` root@ite60-henry-perf02:/data/esearch/data/iTE/nodes/0/indices/report# ls 0 1 2 3 4 _state root@ite60-henry-perf02:/data/esearch/data/iTE/nodes/0/indices/report# du -h . 1.4G ./3/index 8.0K ./3/_state 14G ./3/translog 16G ./3 1.4G ./2/index 8.0K ./2/_state 14G ./2/translog 16G ./2 1.4G ./1/index 8.0K ./1/_state 14G ./1/translog 16G ./1 1.5G ./0/index 8.0K ./0/_state 189M ./0/translog 1.6G ./0 8.0K ./_state 1.5G ./4/index 8.0K ./4/_state 14G ./4/translog 16G ./4 63G . ``` Inside the translog folders I see one huge log file. For example: ``` root@ite60-henry-perf02:/data/esearch/data/iTE/nodes/0/indices/report# ls -l 1/translog total 14523980 -rwxrwxrwx 1 esearch esearch 20 Feb 1 05:30 translog-15.ckp -rwxrwxrwx 1 esearch esearch 43 Nov 21 05:22 translog-15.tlog -rwxr-xr-x 1 esearch esearch 20 Feb 6 04:03 translog-16.ckp -rwxrwxrwx 1 esearch esearch 43 Feb 1 05:30 translog-16.tlog -rwxr-xr-x 1 esearch esearch 20 Feb 6 05:30 translog-17.ckp -rw-r--r-- 1 esearch esearch 43 Feb 6 04:03 translog-17.tlog -rw-r--r-- 1 esearch esearch 14872489859 Feb 7 19:26 translog-18.tlog -rwxrwxrwx 1 esearch esearch 20 Nov 15 18:39 translog-1.ckp -rwxrwxrwx 1 esearch esearch 20 Nov 15 19:08 translog-2.ckp -rwxrwxrwx 1 esearch esearch 20 Feb 7 19:26 translog.ckp ``` Over time those big files keeps growing. Appreciate any pointers on what to look at or what to set. Thanks. ---
**Author:** ![rellimcire](https://avatars.discourse-cdn.com/v4/letter/r/c67d28/32.png) [@rellimcire](https://discuss.elastic.co/u/rellimcire)\ **Post date:** [February 7, 2017, 7:27pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/2 "2017-02-07T19:27:20Z")
I flushed (POST /report/\_flush). Took 14s, cleared 56Gb and rotated translog (now have translog-19, which again continues to grow. ---
**Author:** ![rellimcire](https://avatars.discourse-cdn.com/v4/letter/r/c67d28/32.png) [@rellimcire](https://discuss.elastic.co/u/rellimcire)\ **Post date:** [February 7, 2017, 9:27pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/3 "2017-02-07T21:27:03Z")
Looks like this is related to [15814](https://github.com/elastic/elasticsearch/issues/15814) and fixed by [15830](https://github.com/elastic/elasticsearch/pull/15830) What is best way to pick up that fix? ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [February 7, 2017, 9:56pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/4 "2017-02-07T21:56:33Z")
Upgrade. 2.0.0 is a long time ago in Elasticsearch terms. It is the first release of the last major version. ---
**Author:** ![rellimcire](https://avatars.discourse-cdn.com/v4/letter/r/c67d28/32.png) [@rellimcire](https://discuss.elastic.co/u/rellimcire)\ **Post date:** [February 7, 2017, 10:01pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/5 "2017-02-07T22:01:51Z")
I understand. We're in a development cycle. Don't want to upgrade just on the hope stuff is fixed. This is the first time we noticed the problem. But it looks like upgrading to 2.2+ will fix, right? ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [February 7, 2017, 10:47pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/6 "2017-02-07T22:47:10Z")
Yes, 2.2+ would fix it. If you are upgrading you might want to get to a more modern version though. ---
**Author:** ![rellimcire](https://avatars.discourse-cdn.com/v4/letter/r/c67d28/32.png) [@rellimcire](https://discuss.elastic.co/u/rellimcire)\ **Post date:** [February 7, 2017, 10:50pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/7 "2017-02-07T22:50:49Z")
Already tested, ES 5 breaks us. We use Jest and they seem to have issues, but might be that we're behind there too. For now a customer situation so ES 5 not an option. (Unlike the entire rest of the world it is still necessary for us to deliver software.) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 7, 2017, 10:51pm UTC](https://discuss.elastic.co/t/huge-transaction-log/74261/8 "2017-03-07T22:51:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.