Unable to set path.data for ES

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to set path.data for ES

shadyabhi
Hi,

I have two mount points: /data1 & /data2. I want to use these two mount
points for all the data stored by ES.

To do that, I added
path.data: ["/data1", "/data2"]
in my elasticsearch.yml.

After that, I restarted ES and still "pgrep -fl elas" shows:

20642 java -Xms4g -Xmx10g -Xss256k -Djava.awt.headless=true
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
-Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
-Des.path.home=/usr/share/java/elasticsearch -cp
:/usr/share/java/elasticsearch/lib/elasticsearch-0.19.12.jar:/usr/share/java/elasticsearch/lib/*:/usr/share/java/elasticsearch/lib/sigar/*
-Des.config=/etc/elasticsearch/elasticsearch.yml
-Des.path.conf=/etc/elasticsearch
-Des.path.home=/usr/share/java/elasticsearch
-Des.path.logs=/var/log/elasticsearch
-Des.path.data=/var/lib/elasticsearch -Des.path.work=/tmp/elasticsearch
-Des.path.plugins=/usr/share/java/elasticsearch/plugins
org.elasticsearch.bootstrap.ElasticSearch

Note the path.data value as "-Des.path.data=/var/lib/elasticsearch". Am
I missing something obvious?

--
Cheers,
Abhijeet R
http://blog.abhijeetr.com

--


Reply | Threaded
Open this post in threaded view
|

Re: Unable to set path.data for ES

Igor Motov-3
The elasticsearch.yml is controlling the settings of the elasticsearch after it's started. The settings that you see in pgrep output are controlled by the script that starts elasticsearch. So, you need to modify parameters of this script. For example, if you are running it on Ubuntu using standard .deb package, you can configure these settings in the /etc/default/elasticsearch file.

On Tuesday, January 15, 2013 8:39:56 AM UTC-5, Abhijeet Rastogi wrote:
Hi,

I have two mount points: /data1 & /data2. I want to use these two mount
points for all the data stored by ES.

To do that, I added
path.data: ["/data1", "/data2"]
in my elasticsearch.yml.

After that, I restarted ES and still "pgrep -fl elas" shows:

20642 java -Xms4g -Xmx10g -Xss256k -Djava.awt.headless=true
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly
-XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
-Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
-Des.path.home=/usr/share/java/elasticsearch -cp
:/usr/share/java/elasticsearch/lib/elasticsearch-0.19.12.jar:/usr/share/java/elasticsearch/lib/*:/usr/share/java/elasticsearch/lib/sigar/*
-Des.config=/etc/elasticsearch/elasticsearch.yml
-Des.path.conf=/etc/elasticsearch
-Des.path.home=/usr/share/java/elasticsearch
-Des.path.logs=/var/log/elasticsearch
-Des.path.data=/var/lib/elasticsearch -Des.path.work=/tmp/elasticsearch
-Des.path.plugins=/usr/share/java/elasticsearch/plugins
org.elasticsearch.bootstrap.ElasticSearch

Note the path.data value as "-Des.path.data=/var/lib/elasticsearch". Am
I missing something obvious?

--
Cheers,
Abhijeet R
http://blog.abhijeetr.com

--
 
 
Reply | Threaded
Open this post in threaded view
|

Re: Unable to set path.data for ES

shadyabhi
Hi Igor,

So, do you mean to say that I have the settings already present in ES?
Is there a way to verify this?

On 01/16/2013 01:06 AM, Igor Motov wrote:

> The elasticsearch.yml is controlling the settings of the elasticsearch
> after it's started. The settings that you see in pgrep output are
> controlled by the script that starts elasticsearch. So, you need to
> modify parameters of this script. For example, if you are running it
> on Ubuntu using standard .deb package, you can configure these
> settings in the /etc/default/elasticsearch file.
>
> On Tuesday, January 15, 2013 8:39:56 AM UTC-5, Abhijeet Rastogi wrote:
>
>     Hi,
>
>     I have two mount points: /data1 & /data2. I want to use these two
>     mount
>     points for all the data stored by ES.
>
>     To do that, I added
>     path.data: ["/data1", "/data2"]
>     in my elasticsearch.yml.
>
>     After that, I restarted ES and still "pgrep -fl elas" shows:
>
>     20642 java -Xms4g -Xmx10g -Xss256k -Djava.awt.headless=true
>     -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
>     -XX:CMSInitiatingOccupancyFraction=75
>     -XX:+UseCMSInitiatingOccupancyOnly
>     -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
>     -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
>     -Des.path.home=/usr/share/java/elasticsearch -cp
>     :/usr/share/java/elasticsearch/lib/elasticsearch-0.19.12.jar:/usr/share/java/elasticsearch/lib/*:/usr/share/java/elasticsearch/lib/sigar/*
>
>     -Des.config=/etc/elasticsearch/elasticsearch.yml
>     -Des.path.conf=/etc/elasticsearch
>     -Des.path.home=/usr/share/java/elasticsearch
>     -Des.path.logs=/var/log/elasticsearch
>     -Des.path.data=/var/lib/elasticsearch
>     -Des.path.work=/tmp/elasticsearch
>     -Des.path.plugins=/usr/share/java/elasticsearch/plugins
>     org.elasticsearch.bootstrap.ElasticSearch
>
>     Note the path.data value as
>     "-Des.path.data=/var/lib/elasticsearch". Am
>     I missing something obvious?
>
>     --
>     Cheers,
>     Abhijeet R
>     http://blog.abhijeetr.com
>
> --
>
>

--
Cheers,
Abhijeet R
http://blog.abhijeetr.com

--


Reply | Threaded
Open this post in threaded view
|

Re: Unable to set path.data for ES

Igor Motov-3
Elasticsearch server can be configured using several methods. In your setup, it can be configured using system properties and config files. The system properties are checked first and based on the system properties elasticsearch finds directory with config files and loads config files from there. Some settings can be overwritten in the config files, but some settings are additive. So, for example, if you specify the path using system properties (that can be configured in /etc/default/elasticsearch file) and then in elasticsearch.yml file, you will end up with combination of both system property path and config file file paths as you data paths. If you have relatively new version of elasticsearch, you can check the effective properties by setting "node" logger to "DEBUG" in /etc/elasticsearch/logging.yml, restarting elasticsearch and checking log file at /var/log/elasticsearch/elasticsearch.log. If you set logger correctly, you will find the line like this in the log file:

[2013-01-16 06:41:44,197][DEBUG][node                     ] [Banner, Betty Ross] using home [/usr/share/elasticsearch], config [/etc/elasticsearch], data [[/var/lib/elasticsearch]], logs [/var/log/elasticsearch], work [/tmp/elasticsearch], plugins [/usr/share/elasticsearch/plugins]

This line shows the effective environment settings that this elasticsearch node was started with.

On Wednesday, January 16, 2013 1:55:52 AM UTC-5, Abhijeet Rastogi wrote:
Hi Igor,

So, do you mean to say that I have the settings already present in ES?
Is there a way to verify this?

On 01/16/2013 01:06 AM, Igor Motov wrote:

> The elasticsearch.yml is controlling the settings of the elasticsearch
> after it's started. The settings that you see in pgrep output are
> controlled by the script that starts elasticsearch. So, you need to
> modify parameters of this script. For example, if you are running it
> on Ubuntu using standard .deb package, you can configure these
> settings in the /etc/default/elasticsearch file.
>
> On Tuesday, January 15, 2013 8:39:56 AM UTC-5, Abhijeet Rastogi wrote:
>
>     Hi,
>
>     I have two mount points: /data1 & /data2. I want to use these two
>     mount
>     points for all the data stored by ES.
>
>     To do that, I added
>     path.data: ["/data1", "/data2"]
>     in my elasticsearch.yml.
>
>     After that, I restarted ES and still "pgrep -fl elas" shows:
>
>     20642 java -Xms4g -Xmx10g -Xss256k -Djava.awt.headless=true
>     -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
>     -XX:CMSInitiatingOccupancyFraction=75
>     -XX:+UseCMSInitiatingOccupancyOnly
>     -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch
>     -Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
>     -Des.path.home=/usr/share/java/elasticsearch -cp
>     :/usr/share/java/elasticsearch/lib/elasticsearch-0.19.12.jar:/usr/share/java/elasticsearch/lib/*:/usr/share/java/elasticsearch/lib/sigar/*
>
>     -Des.config=/etc/elasticsearch/elasticsearch.yml
>     -Des.path.conf=/etc/elasticsearch
>     -Des.path.home=/usr/share/java/elasticsearch
>     -Des.path.logs=/var/log/elasticsearch
>     -Des.path.data=/var/lib/elasticsearch
>     -Des.path.work=/tmp/elasticsearch
>     -Des.path.plugins=/usr/share/java/elasticsearch/plugins
>     org.elasticsearch.bootstrap.ElasticSearch
>
>     Note the path.data value as
>     "-Des.path.data=/var/lib/elasticsearch". Am
>     I missing something obvious?
>
>     --
>     Cheers,
>     Abhijeet R
>     http://blog.abhijeetr.com
>
> --
>
>

--
Cheers,
Abhijeet R
http://blog.abhijeetr.com

--