【ElasticSearch/Linux】ES常见错误:node.lock

【出错原因】

之前启动的ES没有正常退出，导致节点锁定

【解决方案】

找出之前ES进程，强行kill掉

【具体步骤】

[ufo@localhost bin]$ ps aux|grep elastic
ufo        6609  2.7 13.6 2755980 136268 pts/1  Sl+  20:07   1:19 /home/ufo/elasticsearch-8.0.0/jdk/bin/java -Xshare:auto -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -Djava.security.manager=allow -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -XX:+ShowCodeDetailsInExceptionMessages -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Dlog4j2.formatMsgNoLookups=true -Djava.locale.providers=SPI,COMPAT --add-opens=java.base/java.io=ALL-UNNAMED -XX:+UseG1GC -Djava.io.tmpdir=/tmp/elasticsearch-5786098406529683019 -XX:+HeapDumpOnOutOfMemoryError -XX:+ExitOnOutOfMemoryError -XX:HeapDumpPath=data -XX:ErrorFile=logs/hs_err_pid%p.log -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m -Xms388m -Xmx388m -XX:MaxDirectMemorySize=203423744 -XX:G1HeapRegionSize=4m -XX:InitiatingHeapOccupancyPercent=30 -XX:G1ReservePercent=15 -Des.path.home=/home/ufo/elasticsearch-8.0.0 -Des.path.conf=/home/ufo/elasticsearch-8.0.0/config -Des.distribution.flavor=default -Des.distribution.type=tar -Des.bundled_jdk=true -cp /home/ufo/elasticsearch-8.0.0/lib/* org.elasticsearch.bootstrap.Elasticsearch
ufo        6852  0.0  0.0  55068     0 pts/1    Sl+  20:08   0:00 /home/ufo/elasticsearch-8.0.0/modules/x-pack-ml/platform/linux-x86_64/bin/controller
ufo       10087  0.0  0.0 112808   964 pts/3    R+   20:55   0:00 grep --color=auto elastic
[ufo@localhost bin]$ kill -9 6609
[ufo@localhost bin]$ ps aux|grep elastic
ufo       10089  0.0  0.0 112808   964 pts/3    R+   20:55   0:00 grep --color=auto elastic
[ufo@localhost bin]

之后，再启动es就没问题了。

END