# Flush syncing on rotated indicies

**URL:** <https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911>\
**Category:** Elasticsearch\
**Created:** [March 6, 2022, 1:16pm UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911 "2022-03-06T13:16:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [March 6, 2022, 1:16pm UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/1 "2022-03-06T13:16:11Z")

</div>

Thinking about running an operation procedure that should do flushed sync on daily 'rotated' indices and wondering...

Would this be a feasible and good idea and what to avoid?

If we after midnight do synced flush per index of 'yesterday' and avoid any future [re]flush operations on such indices, would this maintain sync markers per daily indices' shards for future faster resyncs/restarts?

Or should we just do a synced flush on all indices at demand eg. before performing a rolling restart etc.?

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 6, 2022, 1:50pm UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/2 "2022-03-06T13:50:03Z")

</div>

There is no need. In recent versions synced flush is deprecated and does nothing more than a regular flush, which Elasticsearch will do automatically anyway.

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [March 7, 2022, 10:57am UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/3 "2022-03-07T10:57:23Z")

</div>

Okay, recent version as in...?  
Are still on v.6.8 here.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 7, 2022, 11:02am UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/4 "2022-03-07T11:02:27Z")

</div>

"Recent" meaning "not past [EOL](https://www.elastic.co/support/eol)", so not including 6.8. I don't recall the details in 6.8 although I don't recall ever seeing anyone else doing periodic synced flushes. If it were me I'd focus on upgrading to 7.x instead.

---

<div class="post-metadata">

**Author:** ![stefws](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stefws/32/6442_2.png) [@stefws](https://discuss.elastic.co/u/stefws)\
**Post date:** [March 7, 2022, 11:30am UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/5 "2022-03-07T11:30:48Z")

</div>

🙂 v.7 is on the road map, but until then I thought of doing nightly syncs...

---

<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:** [April 4, 2022, 11:31am UTC](https://discuss.elastic.co/t/flush-syncing-on-rotated-indicies/298911/6 "2022-04-04T11:31:02Z")

</div>

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