# Elasticsearch Index Engine

**URL:** <https://discuss.elastic.co/t/elasticsearch-index-engine/12209>\
**Category:** Elasticsearch\
**Created:** [May 31, 2013, 1:54pm UTC](https://discuss.elastic.co/t/elasticsearch-index-engine/12209 "2013-05-31T13:54:58Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ankit\_Jain](https://avatars.discourse-cdn.com/v4/letter/a/96bed5/32.png) [@Ankit\_Jain](https://discuss.elastic.co/u/Ankit_Jain)\
**Post date:** [May 31, 2013, 1:54pm UTC](https://discuss.elastic.co/t/elasticsearch-index-engine/12209/1 "2013-05-31T13:54:58Z")

</div>

Excerpt from the Elastic search API:  
[http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/](http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/)

It says:

The refresh API allows to explicitly refresh one or more index, making all  
operations performed since the last refresh available for search. _The  
(near) real-time capabilities depend on the index engine used. For example,  
the robin one requires refresh to be called_, but by default a refresh is  
scheduled periodically.

I wanted to ask that do we've any other index engine other than robin where  
i can try out the refresh capabilities.

Thanks

--  
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).

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [June 1, 2013, 1:17am UTC](https://discuss.elastic.co/t/elasticsearch-index-engine/12209/2 "2013-06-01T01:17:38Z")

</div>

ha! this brings back memories, whe ES was created the idea was that it would possibly have multiple engines in a similar manner to other systems. in practice, it ended up having a single implementation, called robin, which us e lucene NRT (near real time search) support, requiring to refresh an index in order to make the latest changes available for search (this is done automatically in ES by default every second)

On Fri, May 31, 2013 at 3:55 PM, Ankit Jain [ankitjaincs06@gmail.com](mailto:ankitjaincs06@gmail.com)  
wrote:

> ## Excerpt from the Elastic search API: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/) It says: The refresh API allows to explicitly refresh one or more index, making all operations performed since the last refresh available for search. _The (near) real-time capabilities depend on the index engine used. For example, the robin one requires refresh to be called_, but by default a refresh is scheduled periodically. I wanted to ask that do we've any other index engine other than robin where i can try out the refresh capabilities. Thanks
> 
> 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).

---

<div class="post-metadata">

**Author:** ![Ankit\_Jain](https://avatars.discourse-cdn.com/v4/letter/a/96bed5/32.png) [@Ankit\_Jain](https://discuss.elastic.co/u/Ankit_Jain)\
**Post date:** [June 3, 2013, 7:45am UTC](https://discuss.elastic.co/t/elasticsearch-index-engine/12209/3 "2013-06-03T07:45:52Z")

</div>

Hi Kimchy,

Thanks for the reply.

If we will use memory store, then after how much time, the in memory data  
is available for search?.

Also, after how much time, the data will be flushed into disk?.

Thanks,  
Ankit

On Saturday, 1 June 2013 06:47:38 UTC+5:30, kimchy wrote:

> ha! this brings back memories, whe ES was created the idea was that it  
> would possibly have multiple engines in a similar manner to other systems.  
> in practice, it ended up having a single implementation, called robin,  
> which us e lucene NRT (near real time search) support, requiring to refresh  
> an index in order to make the latest changes available for search (this is  
> done automatically in ES by default every second)
> 
> On Fri, May 31, 2013 at 3:55 PM, Ankit Jain \<[ankitj...@gmail.com](mailto:ankitj...@gmail.com)\<javascript:\>
> 
> > wrote:
> 
> > Excerpt from the Elastic search API:  
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/)
> > 
> > It says:
> > 
> > The refresh API allows to explicitly refresh one or more index, making  
> > all operations performed since the last refresh available for search. _The  
> > (near) real-time capabilities depend on the index engine used. For example,  
> > the robin one requires refresh to be called_, but by default a refresh  
> > is scheduled periodically.
> > 
> > I wanted to ask that do we've any other index engine other than robin  
> > where i can try out the refresh capabilities.
> > 
> > Thanks
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > 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).

---

<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, 2:33am UTC](https://discuss.elastic.co/t/elasticsearch-index-engine/12209/4 "2017-07-06T02:33:22Z")

</div>


