Elasticsearch deployment on kubernetes using Persistent Volume

Question

I am trying to deploy a Elasticsearch cluster(replicas: 3) using Statefulset in kubernetes and need to store the Elasticsearch data in a Persistent Volume (PV). Since each Elasticsearch instance has its own data folder, I need to have separate data folder for each replica in the PV. I am trying to use volumeClaimTemplates and mountPath: /usr/share/elasticsearch/data but this is resulting in an error: pod has unbound immediate PersistentVolumeClaims in the second pod. Hence how can I achieve this using Statefulset?

Thanks in advance.

[pod has unbound PersistentVolumeClaims](https://stackoverflow.com/questions/52668938/pod-has-unbound-persistentvolumeclaims) — Kamol Hasan, Oct 11 '19 at 11:26

Mark · Answer 1 · 2019-10-14T12:39:06.233

2

There is no information how you are trying to install elastic-search however: As an example please follow:

As per documentation for StatefulSet - limitations:

The storage for a given Pod must either be provisioned by a PersistentVolume Provisioner based on the requested storage class, or pre-provisioned by an admin.

This looks like your example, problem with dynamic storage provisioning.

Please verify storage class, if pv and pvc were created and bind together and storage class in volumeClaimTemplates:

    volumeMounts:
      - name: "elasticsearch-master"
        mountPath: /usr/share/elasticsearch/data
 volumeClaimTemplates:
  - metadata:
      name: elasticsearch-master
    spec:
      accessModes:
      - ReadWriteOnce
      storageClassName: name #please refer to this settings to see if you are using default storage class. In other case you should spceify this parameter manually
      resources:
        requests:
          storage: 30Gi

Hope this help.

edited Oct 14 '19 at 12:39

answered Oct 14 '19 at 12:22

Mark

3,644
6
23

I have defined a PV which uses NFS and would like to store the data folder of each instance of elasticsearch statefulset on that PV. – Newbie Oct 15 '19 at 05:50
So please provide more details, `kubectl get pods,sc,pvc,pvc -o wide`, for the failed pod please use `kubectl describe pod your_failed_pod` also please provide more details about your elastic search deployment – Mark Oct 15 '19 at 07:28
@Newbie have you solved the issue , I am stuck in the same issue https://stackoverflow.com/questions/76819345/elasticsearch-statefulset-replica-not-able-to-claim-persistent-volume-data/76819526#76819526 – dante alighieri Aug 02 '23 at 13:01

score 0 · Answer 2 · answered Oct 11 '19 at 11:43

If you are using dynamic provisioning then you can get the volume created automatically at backend, like disk is storage for PVs in Azure ( for Read Write Once kind of operations), else you need to create that manually

Once you create the volume, just create a pvc in the appropriate namespace which is of size matching the pv, then you are just supposed to pass the volume name in pvc definition, it will get bound automatically.

You can try something like this -

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: claimName
  namespace: namespace
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: default
  volumeName: pv-volumeName
status:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 1Gi

Please share if you still face issues

Elasticsearch deployment on kubernetes using Persistent Volume

2 Answers2