# Document count mismatch in shards

**URL:** <https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640>\
**Category:** Elasticsearch\
**Created:** [November 22, 2017, 5:24am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640 "2017-11-22T05:24:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [November 22, 2017, 5:24am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/1 "2017-11-22T05:24:18Z")

</div>

HI team,

We are often facing doc\_count mismatch between primary and replica shards, Is there any solution for this ?

FYI, we are using elasticsearch 1.3.7 and now working hardly for upgradation.

Please suggest us and help on this!!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 22, 2017, 6:04am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/2 "2017-11-22T06:04:51Z")

</div>

Set number of replica to 0 then set it back to 1?

Note that it will copy a lot of data between nodes again.

---

<div class="post-metadata">

**Author:** ![Balamurali](https://avatars.discourse-cdn.com/v4/letter/b/90db22/32.png) [@Balamurali](https://discuss.elastic.co/u/Balamurali)\
**Post date:** [November 22, 2017, 6:41am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/3 "2017-11-22T06:41:36Z")

</div>

Is there is any possibility for data loss after changing replica count?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 22, 2017, 7:06am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/4 "2017-11-22T07:06:38Z")

</div>

Might be. If the primary shard does not have all the data, then yes.  
If you have a major outage while you do this, then yes.

---

<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:** [November 22, 2017, 8:08am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/5 "2017-11-22T08:08:26Z")

</div>

Version 1.3.7 is very, very old and there is a lot of work that has gone into improving resiliency, consistency and avoiding split-brain scenarios since then, so I would recommend you to upgrade as soon as possible.

---

<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:** [December 20, 2017, 8:08am UTC](https://discuss.elastic.co/t/document-count-mismatch-in-shards/108640/6 "2017-12-20T08:08:40Z")

</div>

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