# Differnt shards giving different results

**URL:** <https://discuss.elastic.co/t/differnt-shards-giving-different-results/188285>\
**Category:** Elasticsearch\
**Created:** [July 1, 2019, 10:23am UTC](https://discuss.elastic.co/t/differnt-shards-giving-different-results/188285 "2019-07-01T10:23:49Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [July 1, 2019, 1:25pm UTC](https://discuss.elastic.co/t/differnt-shards-giving-different-results/188285/7 "2019-07-01T13:25:45Z")

</div>

This very closely-related question seems to be due to inconsistent synonyms on the nodes, or synonyms that changed over time:

> [@Different primary and replica shard size](https://discuss.elastic.co/t/different-primary-and-replica-shard-size/187331/7):
>
> A good thought. Yes, inconsistent synonyms files can indeed result in inconsistent search results. Elasticsearch will use the current synonym file for searches and for indexing new documents but will not re-index any old documents, and this can leave your index in a very strange state. I think reindexing would be wise.

Does that apply in your case too?

---

_[View the full topic](https://discuss.elastic.co/t/differnt-shards-giving-different-results/188285)._
