K
Q

What updates should be made in Elasticsearch statefulset file for version 8.0.0?

2/16/2022

I had created the a stateful set file for Elasticsearch 7.16.1 but on upgrading the ELK stack to 8.0.0, I get this error in the logs of the elastic pod:- "java.lang.IllegalStateException: failed to obtain node locks, tried [/usr/share/elasticsearch/data]; maybe these locations are not writable or multiple nodes were started on the same data path?

Likely root cause: 

java.nio.file.NoSuchFileException: /usr/share/elasticsearch/data/node.lock"

Elastic pod error

Kibana pod gives this error:- 

"curl: (7) Failed to connect to elastic-cluster port 9200: Connection refused"

Kibana pod error

I didn't get this error with the 7.16.1 version.

Should I make some changes in the statefulset files or any other files? Please help me solve this.

-- Dolly
elastic-stack
elasticsearch
elk
kibana
kubernetes

Similar Questions

Kubernetes: Which Ingress Controller are permitted to use for grpc service without TLS?
How to move k3s' ingress to another port
Running Kubernetes across cloud providers
Container in dind access another container in the same Kubernetes pod
fatal: unable to access 'https://gitlab-ci-token:[MASKED]@gitlab.mydomain.com/xxx.git/': SSL certificate problem: unable to get issuer certificate

2 Answers

2/17/2022

most likely the folder /usr/share/elasticsearch/data doesnt have required permissions.

include init container in your deployment manifest and provide appropriate permissions needed by the elastic process to write the index data.

-- P Ekambaram
Source: StackOverflow
2/18/2022

Adding the following initContainers in my statefulset.yaml fixed the issue for me:

initContainers:
- name: fix-permissions

  image: busybox

  command: ["sh", "-c", "chown -R 1000:1000 /usr/share/elasticsearch/data"]

  securityContext:

          privileged: true

  volumeMounts:

  - name: local-storage

    mountPath: /usr/share/elasticsearch/data
-- Dolly
Source: StackOverflow