Elasticsearch pod fails to start up due to "failed to obtain node locks" error
Issue
- One of the
Elasticsearch
pod is doesn't have all the containers in ready state:
elasticsearch-cdm-5go9ltbm-1-5b49db9966-8bfq7 1/2 Running 21 1h29m <<========
elasticsearch-cdm-5go9ltbm-2-7f8566959c-pxzrr 2/2 Running 0 1h29m
elasticsearch-cdm-5go9ltbm-3-bdd7f8668-g25js 2/2 Running 0 1h29m
Elasticsearch
pod log shows "failed to obtain node locks" error:
2021-08-11T01:31:21.727369283Z java.lang.IllegalStateException: failed to obtain node locks, tried [[/elasticsearch/persistent/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])?
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.