Moving data directory

j_barrett_strausser · February 19, 2013, 5:22am

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

dadoonet · February 19, 2013, 6:27am

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data directory to a new directory ? Can I simple 'cp /old/data /new/data' without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

j_barrett_strausser · February 19, 2013, 4:49pm

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and
make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch
is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

@barrettsmash

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

dadoonet · February 19, 2013, 4:59pm

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I mean that your modifications in elasticsearch.yml are probably not read as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each directory over ending up with

/bigdata/elasticsearch/data/graylog2 and /bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:
On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data directory to a new directory ? Can I simple 'cp /old/data /new/data' without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

j_barrett_strausser · February 19, 2013, 5:09pm

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to the
new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of the
elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would still
start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I
mean that your modifications in elasticsearch.yml are probably not read as
a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and
make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch
is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

@barrettsmash

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

dadoonet · February 19, 2013, 5:12pm

Can you paste here your path*** lines ?

David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at : http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:
graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I mean that your modifications in elasticsearch.yml are probably not read as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each directory over ending up with

/bigdata/elasticsearch/data/graylog2 and /bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:
On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data directory to a new directory ? Can I simple 'cp /old/data /new/data' without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

j_barrett_strausser · February 19, 2013, 5:22pm

#################################### Paths
####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be striped

across

the locations (a la RAID 0) on a file level, favouring locations with

most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:

Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to
the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of
the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would still
start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I
mean that your modifications in elasticsearch.yml are probably not read as
a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and
make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch
is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

@barrettsmash

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

dadoonet · February 19, 2013, 5:27pm

I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

#################################### Paths ####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be striped across

the locations (a la RAID 0) on a file level, favouring locations with most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:
Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at : http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:
graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I mean that your modifications in elasticsearch.yml are probably not read as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each directory over ending up with

/bigdata/elasticsearch/data/graylog2 and /bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:
On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data directory to a new directory ? Can I simple 'cp /old/data /new/data' without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

j_barrett_strausser · February 19, 2013, 5:28pm

Let me figure out how to do that and I'll get back to you with the results.

Thanks for the help so far though.

-barrett

On Tue, Feb 19, 2013 at 12:27 PM, David Pilato david@pilato.fr wrote:

I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

#################################### Paths
####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be

striped across

the locations (a la RAID 0) on a file level, favouring locations with

most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:

Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to
the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of
the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would
still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I
mean that your modifications in elasticsearch.yml are probably not read as
a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch
and make the chmod.

In my elasticsearch.yml I pointed path.data to
/bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in
/var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

@barrettsmash

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

j_barrett_strausser · February 19, 2013, 5:43pm

The level was already set at DEBUG in my logging.yml

On Tue, Feb 19, 2013 at 12:28 PM, j.barrett strausser <
j.barrett.strausser@gmail.com> wrote:

Let me figure out how to do that and I'll get back to you with the results.

Thanks for the help so far though.

-barrett

On Tue, Feb 19, 2013 at 12:27 PM, David Pilato david@pilato.fr wrote:

I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

#################################### Paths
####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be

striped across

the locations (a la RAID 0) on a file level, favouring locations with

most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:

Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to
the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of
the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would
still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I
mean that your modifications in elasticsearch.yml are probably not read as
a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch
and make the chmod.

In my elasticsearch.yml I pointed path.data to
/bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in
/var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

--

@barrettsmash

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

dadoonet · February 19, 2013, 5:50pm

Can Gist your logs?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:43, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

The level was already set at DEBUG in my logging.yml

On Tue, Feb 19, 2013 at 12:28 PM, j.barrett strausser j.barrett.strausser@gmail.com wrote:
Let me figure out how to do that and I'll get back to you with the results.

Thanks for the help so far though.

-barrett

On Tue, Feb 19, 2013 at 12:27 PM, David Pilato david@pilato.fr wrote:
I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

#################################### Paths ####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be striped across

the locations (a la RAID 0) on a file level, favouring locations with most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:
Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at : http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:
graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?). I mean that your modifications in elasticsearch.yml are probably not read as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" j.barrett.strausser@gmail.com a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each directory over ending up with

/bigdata/elasticsearch/data/graylog2 and /bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch and make the chmod.

In my elasticsearch.yml I pointed path.data to /bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in /var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:
On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data directory to a new directory ? Can I simple 'cp /old/data /new/data' without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

j_barrett_strausser · February 19, 2013, 7:15pm

That is the log from a successful start, meaning ; I had my "new" data
path commented out.
Uncommenting the new data path results in no logs being put in the file.

github.com

bstrausser/elasticsearchdebug/blob/master/graylog2.log


[2013-02-19 14:03:00,881][INFO ][node                     ] [Slab] {0.20.4}[6809]: initializing ...
[2013-02-19 14:03:00,881][DEBUG][node                     ] [Slab] using home [/usr/share/elasticsearch], config [/etc/elasticsearch], data [[/var/lib/elasticsearch]], logs [/var/log/elasticsearch], work [/tmp/elasticsearch], plugins [$
[2013-02-19 14:03:00,887][INFO ][plugins                  ] [Slab] loaded [], sites []
[2013-02-19 14:03:00,898][DEBUG][common.compress.lzf      ] using [UnsafeChunkDecoder] decoder
[2013-02-19 14:03:01,172][DEBUG][env                      ] [Slab] using node location [[/var/lib/elasticsearch/graylog2/nodes/0]], local_node_id [0]
[2013-02-19 14:03:02,434][DEBUG][threadpool               ] [Slab] creating thread_pool [generic], type [cached], keep_alive [30s]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [index], type [cached], keep_alive [5m]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [bulk], type [cached], keep_alive [5m]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [get], type [cached], keep_alive [5m]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [search], type [cached], keep_alive [5m]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [percolate], type [cached], keep_alive [5m]
[2013-02-19 14:03:02,453][DEBUG][threadpool               ] [Slab] creating thread_pool [management], type [scaling], min [1], size [5], keep_alive [5m]
[2013-02-19 14:03:02,456][DEBUG][threadpool               ] [Slab] creating thread_pool [flush], type [scaling], min [1], size [10], keep_alive [5m]
[2013-02-19 14:03:02,458][DEBUG][threadpool               ] [Slab] creating thread_pool [merge], type [scaling], min [1], size [20], keep_alive [5m]
[2013-02-19 14:03:02,458][DEBUG][threadpool               ] [Slab] creating thread_pool [refresh], type [scaling], min [1], size [10], keep_alive [5m]
[2013-02-19 14:03:02,458][DEBUG][threadpool               ] [Slab] creating thread_pool [cache], type [scaling], min [1], size [4], keep_alive [5m]
[2013-02-19 14:03:02,458][DEBUG][threadpool               ] [Slab] creating thread_pool [snapshot], type [scaling], min [1], size [5], keep_alive [5m]
[2013-02-19 14:03:02,476][DEBUG][transport.netty          ] [Slab] using worker_count[2], port[9300-9400], bind_host[null], publish_host[null], compress[false], connect_timeout[30s], connections_per_node[2/6/1], receive_predictor[512kb$
[2013-02-19 14:03:02,484][DEBUG][discovery.zen.ping.multicast] [Slab] using group [224.2.2.4], with port [54328], ttl [3], and address [null]

This file has been truncated. show original

On Tue, Feb 19, 2013 at 12:50 PM, David Pilato david@pilato.fr wrote:

Can Gist your logs?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:43, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

The level was already set at DEBUG in my logging.yml

On Tue, Feb 19, 2013 at 12:28 PM, j.barrett strausser <
j.barrett.strausser@gmail.com> wrote:

Let me figure out how to do that and I'll get back to you with the
results.

Thanks for the help so far though.

-barrett

On Tue, Feb 19, 2013 at 12:27 PM, David Pilato david@pilato.fr wrote:

I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

#################################### Paths
####################################

Path to directory containing configuration (this file and logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be

striped across

the locations (a la RAID 0) on a file level, favouring locations with

most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:

Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data to
the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid of
the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would
still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.fr wrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?).
I mean that your modifications in elasticsearch.yml are probably not read
as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied each
directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch
and make the chmod.

In my elasticsearch.yml I pointed path.data to
/bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in
/var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.fr wrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current data
directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

@barrettsmash

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

j_barrett_strausser · February 19, 2013, 9:27pm

Turned out to be a whitespace issue in my elastisearch.yaml.

I wish it had been easier to locate this issue.

In any case, I ended up doing the following in /etc/init.d/elasticsearch

On the start-stop-daemon command I modified the following

original :

--exec /bin/bash -- -c "$DAEMON $DAEMON_ARGS"

modified:

--exec /bin/bash -- -c "$DAEMON $DAEMON_ARGS >
/var/log/elasticsearch/startup.log 2>&1"

I then saw the following error :

Setup Failed ...

SettingsException[Failed to load settings from
[file:/etc/elasticsearch/elasticsearch.yml]]
ParserException[while parsing a block mapping; expected , but found BlockMappingStart]

which I recognized as a yaml error.

-barrett

On Tue, Feb 19, 2013 at 2:15 PM, j.barrett strausser <
j.barrett.strausser@gmail.com> wrote:

That is the log from a successful start, meaning ; I had my "new" data
path commented out.
Uncommenting the new data path results in no logs being put in the file.

https://github.com/bstrausser/elasticsearchdebug/blob/master/graylog2.log

On Tue, Feb 19, 2013 at 12:50 PM, David Pilato david@pilato.fr wrote:

Can Gist your logs?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:43, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

The level was already set at DEBUG in my logging.yml

On Tue, Feb 19, 2013 at 12:28 PM, j.barrett strausser <
j.barrett.strausser@gmail.com> wrote:

Let me figure out how to do that and I'll get back to you with the
results.

Thanks for the help so far though.

-barrett

On Tue, Feb 19, 2013 at 12:27 PM, David Pilato david@pilato.fr wrote:

I just test that on 0.20.4 and have no problem moving dir.
Perhaps you should log in DEBUG?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:22, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

#################################### Paths
####################################

Path to directory containing configuration (this file and

logging.yml):

path.conf: /path/to/conf

Path to directory where to store index data allocated for this node.

path.data: /bigdata/elasticsearch/data

Can optionally include more than one location, causing data to be

striped across

the locations (a la RAID 0) on a file level, favouring locations with

most free

space on creation. For example:

path.data: /path/to/data1,/path/to/data2

Path to temporary files:

path.work: /path/to/work

Path to log files:

path.logs: /bigdata/elasticsearch/log

Path to where plugins are installed:

path.plugins: /path/to/plugins

Running ls -la on /bigdata/elasticsearch/data gives

drwxrwxr-x 4 elasticsearch elasticsearch 4096 Feb 19 11:14 data

On Tue, Feb 19, 2013 at 12:12 PM, David Pilato david@pilato.fr wrote:

Can you paste here your path*** lines ?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 18:09, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

For the record I am on

Ubunutu 12.10 running the deb found at :
http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-0.20.4.deb
I had no issues starting or indexing prior to changing the path.data
to the new path. If I comment it out (revert to default) ES starts up again.

Correct on the first question. I realize I could essentially get rid
of the elasticsearch directory inside of /data

I don't see any output in /var/log/elasticsearch.

I am starting ES via /etc/init.d/elasticsearch start

If it wasn't respecting the paths in the .yml then I assume it would
still start as it should use the default paramaters.

-b

On Tue, Feb 19, 2013 at 11:59 AM, David Pilato david@pilato.frwrote:

graylog2 and elasticsearch dirs are relative to cluster names.

I think you first started a cluster using defaults and then move the
cluster name to graylog2, don't you?

That said, what does logs are telling?
How did you start Elasticsearch?

Are you sure that path are not set externally (in a launch script ?).
I mean that your modifications in elasticsearch.yml are probably not read
as a script already defines paths.

Does it help?

--
David Pilato | Technical Advocate | *Elasticsearch.com http://elasticsearch.com/
*
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
| @scrutmydocs https://twitter.com/scrutmydocs

Le 19 févr. 2013 à 17:49, "j.barrett strausser" <
j.barrett.strausser@gmail.com> a écrit :

Bit of a snag

My data directory was previously ( I assume it was at least)

/var/lib/elasticsearch with

../graylog2
../elasticsearch

being the child items

I wanted to move them to /bigdata/elasticsearch/data so I copied
each directory over ending up with

/bigdata/elasticsearch/data/graylog2 and
/bigdata/elasticsearch/data/elasticsearch

I then chowned /big/data/elasticsearch to elasticsearch:elasticsearch
and make the chmod.

In my elasticsearch.yml I pointed path.data to
/bigdata/elasticsearch/data

Running /etc/init.d/elasticsearch results in a failed start.

I'm sure I messed something trivial up. Nothing in
/var/log/elasticsearch is being helpful though.

-barrett

On Tue, Feb 19, 2013 at 1:27 AM, David Pilato david@pilato.frwrote:

On a stopped Elasticsearch node, yes.

You can test it on a test cluster.

--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 19 févr. 2013 à 06:22, j.barrett.strausser@gmail.com a écrit :

Apologies for the simple question.

What would be the procedure for moving the data from the current
data directory to a new directory ? Can I simple 'cp /old/data /new/data'
without worrying about corruption someplace?

Is the only configuration point really

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch

Thanks

-b

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

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

--

bearrito (Barrett Strausser) · GitHub
@barrettsmash

--

@barrettsmash

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