# Weid bahavior: query returns different result sets at different times

**URL:** <https://discuss.elastic.co/t/weid-bahavior-query-returns-different-result-sets-at-different-times/36944>\
**Category:** Elasticsearch\
**Created:** [December 11, 2015, 6:23am UTC](https://discuss.elastic.co/t/weid-bahavior-query-returns-different-result-sets-at-different-times/36944 "2015-12-11T06:23:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jchen2000](https://avatars.discourse-cdn.com/v4/letter/j/b77776/32.png) [@jchen2000](https://discuss.elastic.co/u/jchen2000)\
**Post date:** [December 11, 2015, 6:23am UTC](https://discuss.elastic.co/t/weid-bahavior-query-returns-different-result-sets-at-different-times/36944/1 "2015-12-11T06:23:23Z")

</div>

working on a project where we query es periodically and with range filters, in order to detect trends (like spikes) of certain conditions.

To make sure all indexed event settle down and we don't miss any of them, we used a 10m query delay (we query events that were indexed at least 10 minutes before they got queried)

Now we found lots of false positives because the query would miss some events during detection time, but later on appears in the result (after say 6 hours).

I thought they might got delayed in the indexing process for whatever reasons, but examining the indexing time (we enabled \_timestamp field) tells that was not the case.

Any hints on how this could happen?

Thanks,  
Fang

---

<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 5, 2017, 11:31pm UTC](https://discuss.elastic.co/t/weid-bahavior-query-returns-different-result-sets-at-different-times/36944/2 "2017-07-05T23:31:53Z")

</div>

Closed on July 5, 2017, 11:31pm UTC