# Accuracy/guarantee around refresh\_interval

**URL:** <https://discuss.elastic.co/t/accuracy-guarantee-around-refresh-interval/205159>\
**Category:** Elasticsearch\
**Created:** [October 24, 2019, 9:47pm UTC](https://discuss.elastic.co/t/accuracy-guarantee-around-refresh-interval/205159 "2019-10-24T21:47:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [October 24, 2019, 9:47pm UTC](https://discuss.elastic.co/t/accuracy-guarantee-around-refresh-interval/205159/1 "2019-10-24T21:47:42Z")

</div>

I have an ES7.2 index set up with a `refresh_interval` of `30s`. Docs get inserted, a notification is sent to a SQS queue with a 31 sec delivery delay, and then a job reads from the queue and does a _search_ against that index. The vast majority of the time, the new doc is searchable as expected. Sometimes though, it's not. When the task gets tried again in a little while, the doc is always there.

Am I just taking `refresh_interval` too literally? Maybe if the cluster is busy and the in-memory buffer is large it could take a few more seconds to get the new segment written and opened?

---

<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:** [November 21, 2019, 9:47pm UTC](https://discuss.elastic.co/t/accuracy-guarantee-around-refresh-interval/205159/2 "2019-11-21T21:47:50Z")

</div>

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