# Forcing shards synchronization

**URL:** <https://discuss.elastic.co/t/forcing-shards-synchronization/313549>\
**Category:** Elasticsearch\
**Created:** [September 2, 2022, 11:49am UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549 "2022-09-02T11:49:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [September 2, 2022, 11:49am UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549/1 "2022-09-02T11:49:08Z")

</div>

Hello There!  
I know that shards are synchronized automatically but is there a way to force synchronization? I'm thinking of command/setting in Kibana/bash script to do fire and do it for me.

---

<div class="post-metadata">

**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:** [September 2, 2022, 6:44pm UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549/2 "2022-09-02T18:44:23Z")

</div>

What is the problem you are looking to solve? As shards are synchronised by default there is no way to force it. Are you perhaps referring to forcing refreshes?

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [September 4, 2022, 6:44pm UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549/3 "2022-09-04T18:44:49Z")

</div>

And what if an error occurs during sync?

---

<div class="post-metadata">

**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:** [September 4, 2022, 6:54pm UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549/4 "2022-09-04T18:54:02Z")

</div>

That is all handled automatically by Elasticsearch. Have a look at [this old blog post](https://www.elastic.co/blog/elasticsearch-sequence-ids-6-0) from the time sequence numbers were introduced in order to improve reliability, error handling and consistency. There may be newer sources I could not find but this describes the rationale behind these improvements.

---

<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:** [October 2, 2022, 6:54pm UTC](https://discuss.elastic.co/t/forcing-shards-synchronization/313549/5 "2022-10-02T18:54:49Z")

</div>

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