# Random hit counts in every time
**URL:** https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596
**Category:** Elasticsearch
**Created:** [July 3, 2017, 7:04am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596 "2017-07-03T07:04:23Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Balamurali](https://discuss.elastic.co/u/Balamurali)
#### Post date: [July 3, 2017, 7:04am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/1 "2017-07-03T07:04:23Z")
Hi All,
We are using elasticsearch 1.3.7 version with 5 data only nodes and 3 master only nodes, now we are working hard on elasticsearch upgrade
Now Facing some miscount issue ,one time same query gets 177 hits and another time getting 0 hits for same query.
getting random results (0 hits or 177 hits ) for every curl execution.
Checked after cache clear also, facing same issue.
please help us to debug this issue.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 3, 2017, 7:08am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/2 "2017-07-03T07:08:07Z")
If you use the [cat shards API](https://www.elastic.co/guide/en/elasticsearch/reference/1.3/cat-shards.html), do all shards of the index you are querying have the same number of documents? Does the count stay consistent if you use a [preference parameter](https://www.elastic.co/guide/en/elasticsearch/reference/1.3/search-request-preference.html) to ensure you always hit the same shards?
---
### Author:  [@Balamurali](https://discuss.elastic.co/u/Balamurali)
#### Post date: [July 3, 2017, 7:29am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/3 "2017-07-03T07:29:49Z")
Thanks @Christian_Dahlqvist , few shards having differ doc\_counts
please suggest us, what can we do now?
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 3, 2017, 7:39am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/4 "2017-07-03T07:39:17Z")
I would recommend that you prioritise upgrading, as a lot of improvements related to resiliency and correctness have gone intro more recent versions. Just because shard A have more documents than shard B does not necessarily mean that shard B does not have documents that are missing from shard A. Setting replica to 0 and then increasing it to 1 again would make the shards consistent, but may lose data. In order to make sure you capture all records, you may need to reindex data while making sure you extract data from all shards using the preference parameter. If you have an external data source that is the master, you could also reindex from that instead.
---
### Author:  [@Balamurali](https://discuss.elastic.co/u/Balamurali)
#### Post date: [July 3, 2017, 8:30am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/5 "2017-07-03T08:30:33Z")
Thanks much @Christian_Dahlqvist
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 31, 2017, 8:30am UTC](https://discuss.elastic.co/t/random-hit-counts-in-every-time/91596/6 "2017-07-31T08:30:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.