# Issue with "Synced Flush" for Elasticsearch (ES) V 1.5.2

**URL:** <https://discuss.elastic.co/t/issue-with-synced-flush-for-elasticsearch-es-v-1-5-2/50237>\
**Category:** Elasticsearch\
**Created:** [May 17, 2016, 3:36pm UTC](https://discuss.elastic.co/t/issue-with-synced-flush-for-elasticsearch-es-v-1-5-2/50237 "2016-05-17T15:36:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![vikram\_yerneni](https://avatars.discourse-cdn.com/v4/letter/v/3ab097/32.png) [@vikram\_yerneni](https://discuss.elastic.co/u/vikram_yerneni)\
**Post date:** [May 17, 2016, 4:05pm UTC](https://discuss.elastic.co/t/issue-with-synced-flush-for-elasticsearch-es-v-1-5-2/50237/3 "2016-05-17T16:05:04Z")

</div>

Yes Christian.. I just saw this in one of the blog post ([Replicas synchronization](https://discuss.elastic.co/t/replicas-synchronization/37091)).  
Well, if thats the case do we know a best possible way to perform the upgrade to newer version of ES without the "synced flush" process? Or is there a different process of upgrading these older versions of ES..??

Please do add your points..

Thanks  
Vikram Y

---

_[View the full topic](https://discuss.elastic.co/t/issue-with-synced-flush-for-elasticsearch-es-v-1-5-2/50237)._