# Inconsistency between primary shard and replicas around \_source

**URL:** <https://discuss.elastic.co/t/inconsistency-between-primary-shard-and-replicas-around--source/99768>\
**Category:** Elasticsearch\
**Created:** [September 7, 2017, 8:29pm UTC](https://discuss.elastic.co/t/inconsistency-between-primary-shard-and-replicas-around--source/99768 "2017-09-07T20:29:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jigarjm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jigarjm/32/858_2.png) [@jigarjm](https://discuss.elastic.co/u/jigarjm)\
**Post date:** [September 7, 2017, 8:29pm UTC](https://discuss.elastic.co/t/inconsistency-between-primary-shard-and-replicas-around--source/99768/1 "2017-09-07T20:29:33Z")

</div>

Elasticsearch: 1.7.4 ( We understand that it is pretty old version)  
Index: foo  
shards: 1  
replicas: 2 (total 3 copies, including primary shard)

In our ES cluster setup with above configuration. We saw inconsistency in query response (either result with docs or none). Digging further we narrowed it down that our primary shard doesn't return result (i.e. when we use ?preference=\_primary\_first )

Looking closer at the docs on primary copy of shard and replicas. there is delta. Primary copy of shard has source of document enabled for all the fields while replicas doesn't have it. desired behavior is to not have source ON for all the fields.

Looking at mapping of that type with ?preference=\_primary\_first and without it. THere is no delta in mapping or setting of index

Upgrading ES version is not trivial in our application side. I would like to know if there was a bug around it which was noticed and fixed before I make stronger upgrade case.

I noticed this discussion: [Inconsistent field mapping -- sometimes string, sometimes long](https://discuss.elastic.co/t/inconsistent-field-mapping-sometimes-string-sometimes-long/39036) which is not the case with us since mapping is registered same in all the copies of shard.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [September 11, 2017, 7:23am UTC](https://discuss.elastic.co/t/inconsistency-between-primary-shard-and-replicas-around--source/99768/2 "2017-09-11T07:23:03Z")

</div>

That Elasticsearch release happened almost two years ago (but more importantly two major versions ago), so I am pretty sure there have been bugfixes in that regard.

The [resiliency status page](https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html) and the `resiliency` github tag are good places to start.

---

<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 9, 2017, 7:23am UTC](https://discuss.elastic.co/t/inconsistency-between-primary-shard-and-replicas-around--source/99768/3 "2017-10-09T07:23:36Z")

</div>

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