Directory Layout Problem

Elastic Stack Elasticsearch
1

Hello.

I found weird situation of* Directory Layout*. (I use ElasticSearch
0.90.0BETA)

We use 3 different 300GB hard disk in one node, and our
index.store.distributor setting is least_used
However, we found that index data is always wrote on the hard disk which is
set as last order of path.data.

For example.. if path.data setting is like below...(each folder
data1,data2,data3 are mount address of three HDD)

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data2, /root/elasticsearch/data/data3*

...then its indexing progress looks like below
*
*
*/dev/xvdc1 309633052 0 309633052 0 %
/root/elasticsearch/data/data1
*
/dev/xvde1 309633052 0 309633052 0 %
/root/elasticsearch/data/data2
/dev/xvdf1 309633052 75066488 218838128 26%
/root/elasticsearch/data/data3

if I changed path.data like below....

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data3, /root/elasticsearch/data/data2*

*then the Use% of */root/elasticsearch/data/data2 become grow.
*
*
As I know, Elastic Search insert the indexed documents to least used
space. but it always input last positioned data location of path.data
setting...
*
*
What should I do with this situation?
Am I need to do something other settings?
*
*
I wait for some helpful answer for this...

best regards.

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

Could you post the output of this command:

curl "localhost:9200/_nodes/stats?clear=true&fs=true&pretty=true"

and your elasticsearch.yml file somewhere?

On Tuesday, March 26, 2013 7:05:07 AM UTC-4, hoong wrote:

Hello.

I found weird situation of* Directory Layout*. (I use Elasticsearch
0.90.0BETA)

We use 3 different 300GB hard disk in one node, and our
index.store.distributor setting is least_used
However, we found that index data is always wrote on the hard disk which
is set as last order of path.data.

For example.. if path.data setting is like below...(each folder
data1,data2,data3 are mount address of three HDD)

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data2, /root/elasticsearch/data/data3*

...then its indexing progress looks like below
*
*
*/dev/xvdc1 309633052 0 309633052 0 %
/root/elasticsearch/data/data1
*
/dev/xvde1 309633052 0 309633052 0 %
/root/elasticsearch/data/data2
/dev/xvdf1 309633052 75066488 218838128 26%
/root/elasticsearch/data/data3

if I changed path.data like below....

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data3, /root/elasticsearch/data/data2*

*then the Use% of */root/elasticsearch/data/data2 become grow.
*
*
As I know, Elastic Search insert the indexed documents to least used
space. but it always input last positioned data location of path.data
setting...
*
*
What should I do with this situation?
Am I need to do something other settings?
*
*
I wait for some helpful answer for this...

best regards.

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

Actually, I think I found the issue. Working on the fix.

On Wednesday, March 27, 2013 9:05:52 AM UTC-4, Igor Motov wrote:

Could you post the output of this command:

curl "localhost:9200/_nodes/stats?clear=true&fs=true&pretty=true"

and your elasticsearch.yml file somewhere?

On Tuesday, March 26, 2013 7:05:07 AM UTC-4, hoong wrote:

Hello.

I found weird situation of* Directory Layout*. (I use Elasticsearch
0.90.0BETA)

We use 3 different 300GB hard disk in one node, and our
index.store.distributor setting is least_used
However, we found that index data is always wrote on the hard disk which
is set as last order of path.data.

For example.. if path.data setting is like below...(each folder
data1,data2,data3 are mount address of three HDD)

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data2, /root/elasticsearch/data/data3*

...then its indexing progress looks like below
*
*
*/dev/xvdc1 309633052 0 309633052 0 %
/root/elasticsearch/data/data1
*
/dev/xvde1 309633052 0 309633052 0 %
/root/elasticsearch/data/data2
/dev/xvdf1 309633052 75066488 218838128 26%
/root/elasticsearch/data/data3

if I changed path.data like below....

  • path.data: /root/elasticsearch/data/data1,
    /root/elasticsearch/data/data3, /root/elasticsearch/data/data2*

*then the Use% of */root/elasticsearch/data/data2 become grow.
*
*
As I know, Elastic Search insert the indexed documents to least used
space. but it always input last positioned data location of path.data
setting...
*
*
What should I do with this situation?
Am I need to do something other settings?
*
*
I wait for some helpful answer for this...

best regards.

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

4

Thank you very much!!!

2013/3/27 Igor Motov imotov@gmail.com

Actually, I think I found the issue. Working on the fix.

On Wednesday, March 27, 2013 9:05:52 AM UTC-4, Igor Motov wrote:

Could you post the output of this command:

curl "localhost:9200/_nodes/stats?**clear=true&fs=true&pretty=**true"

and your elasticsearch.yml file somewhere?

On Tuesday, March 26, 2013 7:05:07 AM UTC-4, hoong wrote:

Hello.

I found weird situation of* Directory Layout*. (I use Elasticsearch
0.90.0BETA)

We use 3 different 300GB hard disk in one node, and our
index.store.distributor **setting is least_used
However, we found that index data is always wrote on the hard disk which
is set as last order of path.data.

For example.. if path.data setting is like below...(each folder
data1,data2,data3 are mount address of three HDD)

  • path.data: /root/elasticsearch/data/data1, /root/elasticsearch/data/data2,
    /root/elasticsearch/data/data3*

...then its indexing progress looks like below
*
*
*/dev/xvdc1 309633052 0 309633052 0 %
/root/elasticsearch/data/data1
*
/dev/xvde1 309633052 0 309633052 0 %
/root/elasticsearch/data/data2
/dev/xvdf1 309633052 75066488 218838128 26%
/root/elasticsearch/data/data3

if I changed path.data like below....

  • path.data: /root/elasticsearch/data/data1, /root/elasticsearch/data/data3,
    /root/elasticsearch/data/data2*

*then the Use% of */root/elasticsearch/data/data2 become grow.
*
*
As I know, Elastic Search insert the indexed documents to least used
space. but it always input last positioned data location of path.data
setting...
*
*
What should I do with this situation?
Am I need to do something other settings?
*
*
I wait for some helpful answer for this...

best regards.

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

--

전동규
연세대학교 정보산업공학과
지능 웹 비즈니스 연구실
jdkclub85@gmail.com / 010-4142-4160

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