# Version 6.3 \_flush not flushing **URL:** \ **Category:** Elasticsearch\ **Created:** [July 10, 2018, 3:34pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386 "2018-07-10T15:34:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![L8apex32](https://avatars.discourse-cdn.com/v4/letter/l/858c86/32.png) [@L8apex32](https://discuss.elastic.co/u/L8apex32)\ **Post date:** [July 10, 2018, 3:34pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386/1 "2018-07-10T15:34:22Z")
We are having trouble with flushing our translog now that we are on version 6.x. We are using default settings, other than our index has refresh\_interval set to 60s. Indices often have huge translogs (1GB) at the end of the hour. It seems the default translog settings in 6.3 would cause a flush to occur automatically. In previous versions, we'd do a \_flush after the indexing was complete for an index, to ensure the translog was processed and removed. The \_flush API does not appear to work now. Any help would be appreciated. ---
**Author:** ![L8apex32](https://avatars.discourse-cdn.com/v4/letter/l/858c86/32.png) [@L8apex32](https://discuss.elastic.co/u/L8apex32)\ **Post date:** [July 10, 2018, 3:43pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386/2 "2018-07-10T15:43:31Z")
I just found the "manage" button in Kibana for the indices. Used it to flush the index and the translog\_size\_in\_bytes did not change. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [July 10, 2018, 3:51pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386/3 "2018-07-10T15:51:09Z")
In Elasticsearch 6.x recovery can be made based on translog, which can be much more efficient than copying full indices, so it is kept around a bit longer than before to facilitate this. This can however be [tuned using index settings](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/index-modules-translog.html#_translog_settings). [This blog post](https://www.elastic.co/blog/elasticsearch-sequence-ids-6-0) provides some additional background. ---
**Author:** ![L8apex32](https://avatars.discourse-cdn.com/v4/letter/l/858c86/32.png) [@L8apex32](https://discuss.elastic.co/u/L8apex32)\ **Post date:** [July 10, 2018, 4:28pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386/4 "2018-07-10T16:28:17Z")
Thanks for the help Christian. In that blog post you referred, it talks about sequence IDs and the default settings translog.retention.size and translog.retention.age. The defaults (512m and 12h) respectively seems to be exceeded. I have indices that are more than 12 hours old, but which still have large translogs. And second, when I issue /index/\_flush, why does that not flush? Shouldn't I still be able to force a flush? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 7, 2018, 4:28pm UTC](https://discuss.elastic.co/t/version-6-3-flush-not-flushing/139386/5 "2018-08-07T16:28:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.