# Refresh rate **URL:** \ **Category:** Elasticsearch\ **Created:** [August 29, 2013, 10:01pm UTC](https://discuss.elastic.co/t/refresh-rate/13401 "2013-08-29T22:01:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\ **Post date:** [August 29, 2013, 10:01pm UTC](https://discuss.elastic.co/t/refresh-rate/13401/1 "2013-08-29T22:01:42Z")
When using replica shards what's the disadvantage of using higher refresh interval. It appears that GET is realtime anyways and will read data from memory if it's not flushed to disk yet. So even if one node fails you still have data available on the other node. -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [August 29, 2013, 10:06pm UTC](https://discuss.elastic.co/t/refresh-rate/13401/2 "2013-08-29T22:06:13Z")
Only GET requests read from the transaction logs. Searches still rely only on the Lucene segments. Cheers, Ivan On Thu, Aug 29, 2013 at 3:01 PM, Mohit Anchlia [mohitanchlia@gmail.com](mailto:mohitanchlia@gmail.com)wrote: > When using replica shards what's the disadvantage of using higher refresh > interval. It appears that GET is realtime anyways and will read data from > memory if it's not flushed to disk yet. So even if one node fails you still > have data available on the other node. > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [August 29, 2013, 10:18pm UTC](https://discuss.elastic.co/t/refresh-rate/13401/3 "2013-08-29T22:18:18Z")
The refresh action flushes Lucene buffers (not necessarily to disk). You can search in the flushed documents only after a refresh, and this refresh is under full control of the user (behind the scenes, ES refreshes also when buffers are full). ES uses Lucene NRT. That is, there is an additional RAM index which keeps the last doc ids for further reference. Note this index will be flushed in an unpredictable manner, only by internal Lucene mechanisms, not by the user. Elasticsearch NRT mends this uncertainty by refreshing every 1s, so you can search and get docs after 1s. Jörg -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Mohit\_Anchlia](https://avatars.discourse-cdn.com/v4/letter/m/848f3c/32.png) [@Mohit\_Anchlia](https://discuss.elastic.co/u/Mohit_Anchlia)\ **Post date:** [August 29, 2013, 11:33pm UTC](https://discuss.elastic.co/t/refresh-rate/13401/4 "2013-08-29T23:33:54Z")
Thanks all for your responses On Thu, Aug 29, 2013 at 3:18 PM, [joergprante@gmail.com](mailto:joergprante@gmail.com) \< [joergprante@gmail.com](mailto:joergprante@gmail.com)\> wrote: > The refresh action flushes Lucene buffers (not necessarily to disk). You > can search in the flushed documents only after a refresh, and this refresh > is under full control of the user (behind the scenes, ES refreshes also > when buffers are full). > > ES uses Lucene NRT. That is, there is an additional RAM index which keeps > the last doc ids for further reference. Note this index will be flushed in > an unpredictable manner, only by internal Lucene mechanisms, not by the > user. > > Elasticsearch NRT mends this uncertainty by refreshing every 1s, so you > can search and get docs after 1s. > > Jörg > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:18am UTC](https://discuss.elastic.co/t/refresh-rate/13401/5 "2017-07-06T02:18:52Z")