How to load /data directory into memory when I start ES

Elastic Stack Elasticsearch
1

I have indexed my data in default index.store configuration (fs). However I
have enough memory to keep all /data directory and I want to load /data
directory into the memory when I start elasticsearch to boost performance.
AFAIK if I change index.store.type to memory, there is no backup in
filesystem and if I need to reboot the server I lose all data indexed in ES.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

Hey

your assumptions are correct regarding the memory setting. If you do not
have the chance to preload your data after creating an in-memory index, you
might want to go with the store type 'mmapfs' (persistent, but using memory
mapped files for reading).
To read more about lucene and MMapDirectory, check out this excellent blog
post The Generics Policeman Blog: Use Lucene’s MMapDirectory on 64bit platforms, please!

Hope this helps

On Sun, Apr 14, 2013 at 6:12 PM, Burak Emre Kabakcı
emrekabakci@gmail.comwrote:

I have indexed my data in default index.store configuration (fs). However
I have enough memory to keep all /data directory and I want to load /data
directory into the memory when I start elasticsearch to boost performance.
AFAIK if I change index.store.type to memory, there is no backup in
filesystem and if I need to reboot the server I lose all data indexed in ES.

--
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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks, the article is awesome for newbies like me. I assume that I need to
re-index my data because elasticsearch doesn't allow me to change
index.store setting for existing index. I will give it a try and compare it
to default filesystem index.store setting.

On Monday, April 15, 2013 10:00:20 AM UTC+3, Alexander Reelsen wrote:

Hey

your assumptions are correct regarding the memory setting. If you do not
have the chance to preload your data after creating an in-memory index, you
might want to go with the store type 'mmapfs' (persistent, but using memory
mapped files for reading).
To read more about lucene and MMapDirectory, check out this excellent blog
post
The Generics Policeman Blog: Use Lucene’s MMapDirectory on 64bit platforms, please!

Hope this helps

On Sun, Apr 14, 2013 at 6:12 PM, Burak Emre Kabakcı <emrek...@gmail.com<javascript:>

wrote:

I have indexed my data in default index.store configuration (fs). However
I have enough memory to keep all /data directory and I want to load /data
directory into the memory when I start elasticsearch to boost performance.
AFAIK if I change index.store.type to memory, there is no backup in
filesystem and if I need to reboot the server I lose all data indexed in ES.

--
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 <javascript:>.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.