I set the logger level to TRACE and get the following loggings. It seems
ES failed obtaining the node lock. But I still have no idea how to solve
it.
[2014-12-06 10:22:00,101][INFO ][node ] [kyle]
version[1.4.0], pid[18889], build[bc94bd8/2014-11-05T14:26:12Z]
[2014-12-06 10:22:00,102][INFO ][node ] [kyle]
initializing ...
[2014-12-06 10:22:00,103][DEBUG][node ] [kyle] using
home [/bos/usr0/yingkaig/downloads/elasticsearch-debug], config
[/bos/usr0/yingkaig/downloads/elasticsearch-debug/config], data
[[/bos/tmp11/yingkaig/index.debug]], logs [/bos/usr0/yingkaig/temp/logs],
work [/bos/usr0/yingkaig/downloads/elasticsearch-debug/work], plugins
[/bos/usr0/yingkaig/downloads/elasticsearch-debug/plugins]
[2014-12-06 10:22:00,111][DEBUG][plugins ] [kyle]
[/bos/usr0/yingkaig/downloads/elasticsearch-debug/plugins] directory does
not exist.
[2014-12-06 10:22:00,112][INFO ][plugins ] [kyle] loaded
[], sites []
[2014-12-06 10:22:00,152][DEBUG][common.compress.lzf ] using encoder
[VanillaChunkDecoder] and decoder[{}]
[2014-12-06 10:22:00,157][TRACE][env ] [kyle]
obtaining node lock on /bos/tmp11/yingkaig/index.debug/debug/nodes/0 ...
On Saturday, December 6, 2014 1:38:38 AM UTC-5, Mark Walkom wrote:
>
> Start the service, do a ps|grep java and grab the command that is called
> then run it manually.
> You may find it returns more info you can use to resolve your issue.
>
> Otherwise you can turn up the logging levels in logging.yml.
>
> On 6 December 2014 at 08:41, Yingkai Gao <[email protected] <javascript:>>
> wrote:
>
>> I'm using ElasticSearch-1.4.0 on CentOS-5.6. It works well if I set the
>> index path.data on local/NFS. However, if I set the path.data on a NAS
>> folder, the node keep stuck after initializing and plugins loading.
>>
>> It looks like this link
>> <http://elasticsearch-users.115913.n3.nabble.com/ElasticSearch-fails-on-NFS-makes-tons-of-empty-directories-in-nodes-td3765236.html>
>>
>> a lot, but I'm using NAS. The node did create the index directories on the
>> NAS path, but it just stopped there.
>>
>> The starting log of ElasticSearch is:
>> [2014-12-05 16:36:12,745][INFO ][node ] [kyle]
>> version[1.4.0], pid[4819], build[bc94bd8/2014-11-05T14:26:12Z]
>> [2014-12-05 16:36:12,747][INFO ][node ] [kyle]
>> initializing ...
>> [2014-12-05 16:36:12,755][INFO ][plugins ] [kyle] loaded
>> [], sites []
>>
>> Using command df, the file system information of the mounted NAS is:
>> nas-2-25:/exports/volume02
>>
>> Anyone has any idea how to fix this problem. I know it is not suggested
>> to use NAS for index, but I have to because the infrastructure problem of
>> our cluster.
>>
>> Thanks,
>> Kyle
>>
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/9388166f-d250-4bb2-9f94-44f40dda338f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/47a5a4d1-7bf9-4e89-ba95-1fd206d5da87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
