docker启动es报错：failed to obtain node locks...-Toy模板网

这篇具有很好参考价值的文章主要介绍了docker启动es报错：failed to obtain node locks...。希望对大家有所帮助。如果存在错误或未考虑完全的地方，请大家不吝赐教，您也可以点击"举报违法"按钮提交疑问。

在学习es时，使用docker启动时发现一直报错：

java.lang.IllegalStateException: failed to obtain node locks, tried [[/usr/share/elasticsearch/data]] with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?
Likely root cause: java.nio.file.AccessDeniedException: /usr/share/elasticsearch/data/nodes/0/node.lock

failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe th,linux,elasticsearch,docker,大数据
查找文章：
（1）node.lock被其他进程使用了，这也是网上大多数的解释。解决方案呢，首先查看es的进程，然后杀掉。
ps aux | grep elastic

kill -9 [pid]

然而我的并没有进程占用
（2）有篇文章写的是目录权限不对
failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe th,linux,elasticsearch,docker,大数据
我的docker启动命令是

docker run -d \
    --name es \
    -e "ES_JAVA_OPTS=-Xms512m -Xmx512m" \
    -e "discovery.type=single-node" \
    -v es-data:/usr/share/elasticsearch/data \
    --privileged \
    --network es-net \
    -p 9200:9200 \
    -p 9300:9300 \
elasticsearch:7.12.1

使用-v参数把docker里的/usr/share/elasticsearch/data 目录挂载到了宿主机的es-data目录里，所以猜测是这个数据卷的问题，把-v参数删掉，再次run发现就可以运行成功了。

原因：找到宿主机挂载的这个数据卷目录,发现nodes目录不知道为什么是101账号，
docker inspect es-data failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe th,linux,elasticsearch,docker,大数据
把这个数据卷的nodes目录删了再重启即可成功，如果不行就把整个数据卷目录删了重试

failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe th,linux,elasticsearch,docker,大数据文章来源地址https://www.toymoban.com/news/detail-545563.html