# Index translog grows past the configured limit **URL:** \ **Category:** Elasticsearch\ **Created:** [January 27, 2016, 3:41pm UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259 "2016-01-27T15:41:19Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![KBuev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kbuev/32/20620_2.png) [@KBuev](https://discuss.elastic.co/u/KBuev)\ **Post date:** [January 27, 2016, 3:41pm UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259/1 "2016-01-27T15:41:19Z")
Hi everyone, I'm new to Elasticsearch and have not been able to find a definite answer to this question: can I set translog flush settings per index or are they only available at the node level? I have several index templates with the following settings: "settings": { "index": { "refresh\_interval": "15s", "number\_of\_shards": "2", "translog": { "flush\_threshold\_size": "2048mb", "sync\_interval": "15s", "flush\_threshold\_period": "30m", "durability": "async" }, "number\_of\_replicas": "2" } }, All other settings (like the number of shards/replicas or the refresh interval) apply correctly but I've seen the transaction log for several indices grow well past the defined limit (and I mean 3-4 times bigger). I know the translog fsync settings are definitely per index but for some reason this little detail leaves me confused. The "flush\_threshold\_size" setting seems to work fine if defined in the elasticsearch.yml file. Are these settings meant to be set only in the node configuration file or do I not understand something about how they work? ---
**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:** [January 27, 2016, 7:27pm UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259/2 "2016-01-27T19:27:40Z")
> [@KBuev](#): > > Are these settings meant to be set only in the node configuration file or do I not understand something about how they work? You can set this per index, but I think you might be running into a known issue: [#15814](https://github.com/elastic/elasticsearch/issues/15814). Can you take a look at the issue and corresponding PR [#15830](https://github.com/elastic/elasticsearch/pull/15830) and see if that fits your situation? ---
**Author:** ![KBuev](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kbuev/32/20620_2.png) [@KBuev](https://discuss.elastic.co/u/KBuev)\ **Post date:** [January 27, 2016, 9:36pm UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259/3 "2016-01-27T21:36:58Z")
> However, if the file copying phase of the recovery takes \>5s > (likely!) or local recovery is slow, the check can run into an exception > and never recover. The end result is that the translog based flush is > completely disabled. That is probably it, since our installation of ES runs on some pretty slow disks (unfortunately) and the recovery phase is indeed long. So I guess I'll use the flush API for now as a workaround if this happens again. ---
**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:** [January 29, 2016, 5:45am UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259/4 "2016-01-29T05:45:56Z")
> [@KBuev](#): > > So I guess I'll use the flush API for now as a workaround if this happens again. Yup. And the aforementioned fix will be released soon. ---
**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:20pm UTC](https://discuss.elastic.co/t/index-translog-grows-past-the-configured-limit/40259/5 "2017-07-05T23:20:29Z")