弹性搜索,无法获取节点锁定,是以下位置可写 [英] Elasticsearch, Failed to obtain node lock, is the following location writable
问题描述
弹性搜索将不会开始使用 ./ bin / elasticsearch
。
它引发了以下异常:
- ElasticsearchIllegalStateException [无法获取节点锁定,以下位置可写吗? [/home/user1/elasticsearch-1.4.4/data/elasticsearch]
我查看了相同的位置和位置具有777个权限,由user1拥有。
ls -al / home / user1 / elasticsearch -1.4.4 / data / elasticsearch
drwxrwxrwx 3 user1 wheel 4096 3月8日13:24。
drwxrwxrwx 3 user1 wheel 4096 3月8日13:00 ..
drwxrwxrwx 52 user1 wheel 4096 3月8日13:51节点
有什么问题?
尝试在linux上运行弹性搜索1.4.4,无root访问。
我收到同样的错误消息,但事情挂载正确,权限都已正确分配。 b
$ b
原来我有一个'孤立'弹性搜索过程,没有被正常停止命令杀死。
我不得不手动杀死进程,然后重新启动弹性搜索工作。
Elasticsearch won't start using ./bin/elasticsearch
.
It raises the following exception:
- ElasticsearchIllegalStateException[Failed to obtain node lock, is the following location writable?: [/home/user1/elasticsearch-1.4.4/data/elasticsearch]
I checked the permissions on the same location and the location has 777 permissions on it and is owned by user1.
ls -al /home/user1/elasticsearch-1.4.4/data/elasticsearch
drwxrwxrwx 3 user1 wheel 4096 Mar 8 13:24 . drwxrwxrwx 3 user1 wheel 4096 Mar 8 13:00 .. drwxrwxrwx 52 user1 wheel 4096 Mar 8 13:51 nodes
What is the problem?
Trying to run elasticsearch 1.4.4 on linux without root access.
I got this same error message, but things were mounted fine and the permissions were all correctly assigned.
Turns out that I had an 'orphaned' elasticsearch process that was not being killed by the normal stop command.
I had to manually kill the process and then restarting elasticsearch worked again.
这篇关于弹性搜索,无法获取节点锁定,是以下位置可写的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!