I've been using ElasticSearch last few months, and due to specifications of one project I have one doubt about configuration.
It's possible to set the path of the index data in the file "elasticsearch.yml".
My question is about the possibility to store the Index Data in external server.
To have ElasticSearch installed on Server1
To have the index data stored in Server2
ElasticSearch installed only in Server1
I know this wouldn't be optimal but some projects hasn't too much queries to ES, so I would like to separate the data from the server where the site is installed.
I've been using Elasticsearch last few months, and due to specifications of
one project I have one doubt about configuration.
It's possible to set the path of the index data in the file
"elasticsearch.yml".
My question is about the possibility to store the Index Data in external
server.
To have Elasticsearch installed on Server1
To have the index data stored in Server2
Elasticsearch installed only in Server1
I know this wouldn't be optimal but some projects hasn't too much queries
to
ES, so I would like to separate the data from the server where the site is
installed.
Hi, you need to create a shared file system. So that the data path of
server2 is accessible from server1 and then provide that data path inside
elasticsearch.yml file.
When you will create a shared file system the data directory of server2
will be seems like it is existing on server1 itself.
Regards,
Bharvi
On Wednesday, 3 September 2014 16:01:46 UTC+5:30, Alvaro Aneiros Veiga
wrote:
Hello,
I've been using Elasticsearch last few months, and due to specifications
of
one project I have one doubt about configuration.
It's possible to set the path of the index data in the file
"elasticsearch.yml".
My question is about the possibility to store the Index Data in external
server.
To have Elasticsearch installed on Server1
To have the index data stored in Server2
Elasticsearch installed only in Server1
I know this wouldn't be optimal but some projects hasn't too much queries
to
ES, so I would like to separate the data from the server where the site is
installed.
Yesterday I built a NFS folder, and set the ElasticSearch index path to this NFS folder, so when I create an index and add data to it, ElasticSearch stores the information in this NFS folder (so the information is stored in a external server) but the speed is not the best (something I was counting on).
Yesterday I built a NFS folder, and set the ElasticSearch index path to this
NFS folder, so when I create an index and add data to it, ElasticSearch
stores the information in this NFS folder (so the information is stored in a
external server) but the speed is not the best (something I was counting
on).
This is because in one project I'm going to have 1 "main" index, wich are going to be in the same place that elasticsearch, but there are some other indices (less important and less used) and these indices are going to be used like 1 time per week or less, so I don't need this indices to be "optimal" and I need to save the data for this indices in an external server to save some disk space.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.