# Marvel / ES query document count major discrepancy

**URL:** <https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873>\
**Category:** Elasticsearch\
**Created:** [November 20, 2014, 7:36pm UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873 "2014-11-20T19:36:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Seid](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@Mike\_Seid](https://discuss.elastic.co/u/Mike_Seid)\
**Post date:** [November 20, 2014, 7:36pm UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873/1 "2014-11-20T19:36:42Z")

</div>

Howdy,

I have been hitting my ES cluster pretty hard of recent and I think it is  
holding up great. In the last few days, I have noticed a major discrepancy  
in the document count that Marvel shows versus that of doing a \_count query  
of the actual ES cluster. Marvel is reporting about 43.9M documents while  
the ES query shows 8.7M. Where would this discrepancy come from? I would  
suspect it is a monitor error on Marvels part, but I'm not sure. Any ideas?

Marvel Screenshot:  
[![](https://dl.dropboxusercontent.com/s/1y39wui96fpjc14/Screenshot%202014-11-20%2009.57.42.png?dl=0) ](https://dl.dropboxusercontent.com/s/1y39wui96fpjc14/Screenshot%202014-11-20%2009.57.42.png?dl=0)

ES Query:  
[http://xxxxxxxxx/pa-2014-11-19/\_count](http://xxxxxxxxx/pa-2014-11-19/_count)  
{

- "count": 8781919,
- 

"\_shards": {  
- "total": 5,  
- "successful": 5,  
- "failed": 0  
}

}

Thanks,

Mike

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/071a26ac-db82-42dc-880b-6165a0d38d30%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/071a26ac-db82-42dc-880b-6165a0d38d30%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [November 22, 2014, 4:41pm UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873/2 "2014-11-22T16:41:27Z")

</div>

Maybe it's counting replicas? Or its own docs? See SPM  
[http://sematext.com/spm/](http://sematext.com/spm/) for an alternative.

## Otis

Monitoring \* Alerting \* Anomaly Detection \* Centralized Log Management  
Solr & Elasticsearch Support \* [http://sematext.com/](http://sematext.com/)

On Thursday, November 20, 2014 2:36:42 PM UTC-5, Mike Seid wrote:

> Howdy,
> 
> I have been hitting my ES cluster pretty hard of recent and I think it is  
> holding up great. In the last few days, I have noticed a major discrepancy  
> in the document count that Marvel shows versus that of doing a \_count query  
> of the actual ES cluster. Marvel is reporting about 43.9M documents while  
> the ES query shows 8.7M. Where would this discrepancy come from? I would  
> suspect it is a monitor error on Marvels part, but I'm not sure. Any ideas?
> 
> Marvel Screenshot:
> 
> [Dropbox - Error - Simplify your life](https://www.dropbox.com/s/1y39wui96fpjc14/Screenshot%202014-11-20%2009.57.42.png?dl=0)
> 
> ES Query:  
> [http://xxxxxxxxx/pa-2014-11-19/\_count](http://xxxxxxxxx/pa-2014-11-19/_count)  
> {
> 
> - "count": 8781919,
> - 
> 
> "\_shards": {  
> - "total": 5,  
> - "successful": 5,  
> - "failed": 0  
> }
> 
> }
> 
> Thanks,
> 
> Mike

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/6d426f13-a847-46b3-a273-62e85a6b5a78%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/6d426f13-a847-46b3-a273-62e85a6b5a78%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\
**Post date:** [November 30, 2014, 11:02pm UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873/3 "2014-11-30T23:02:51Z")

</div>

Hi Mike,

That number includes all the docs currently in the index, including deleted  
docs which are not yet physically merged away (the same as the ES Stats API  
does, check the delete stats in the same part). Did you do some documents  
deletion before checking?

Cheers,  
Boaz

On Thursday, November 20, 2014 8:36:42 PM UTC+1, Mike Seid wrote:

> Howdy,
> 
> I have been hitting my ES cluster pretty hard of recent and I think it is  
> holding up great. In the last few days, I have noticed a major discrepancy  
> in the document count that Marvel shows versus that of doing a \_count query  
> of the actual ES cluster. Marvel is reporting about 43.9M documents while  
> the ES query shows 8.7M. Where would this discrepancy come from? I would  
> suspect it is a monitor error on Marvels part, but I'm not sure. Any ideas?
> 
> Marvel Screenshot:
> 
> [Dropbox - File Deleted - Simplify your life](https://www.dropbox.com/s/1y39wui96fpjc14/Screenshot%202014-11-20%2009.57.42.png?dl=0)
> 
> ES Query:  
> [http://xxxxxxxxx/pa-2014-11-19/\_count](http://xxxxxxxxx/pa-2014-11-19/_count)  
> {
> 
> - "count": 8781919,
> - 
> 
> "\_shards": {  
> - "total": 5,  
> - "successful": 5,  
> - "failed": 0  
> }
> 
> }
> 
> Thanks,
> 
> Mike

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ca1b066c-e5c5-428a-aee4-a35bb2bff1a4%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ca1b066c-e5c5-428a-aee4-a35bb2bff1a4%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![DaltonVidra](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@DaltonVidra](https://discuss.elastic.co/u/DaltonVidra)\
**Post date:** [December 1, 2014, 9:29am UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873/4 "2014-12-01T09:29:20Z")

</div>

As soon as we surf the internet and looking for the jammer products we can see that there are various types of signal jammers that are for sale in the market now such as the mobile phone jammers, **[gps jammers for sale](http://www.jammerinthebox.com/categories/GPS_Signal_Jammer/)**, wifi jammers, UHF jammers, the multi-functional signal jammers and so many others kinds of signal jammers for sale as well. And what people now need to do is just select the best one according to their needs.

---

<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:** [July 6, 2017, 12:46am UTC](https://discuss.elastic.co/t/marvel-es-query-document-count-major-discrepancy/20873/5 "2017-07-06T00:46:57Z")

</div>


