InfluxDB Cluster PVC[meta and data], Can be created in AWS EFS / NFS storage framework !! about influxdb-cluster

[chengshiwen]

@MohamedShaj InfluxDB Cluster is an alternative to InfluxDB Enterprise and supports high availability (For high availability, installations must have at least two data nodes. The number of data nodes in your cluster must be the same as your highest replication factor. Any replication factor greater than two gives you additional fault tolerance and query capacity within the cluster.).

So NFS/EFS is not required, because the storage of each data node is completely independent and does not require network sharing. For details, please refer to the official documentation.

For the influx cluster helm chart, you just modify the configuration items like storageClass and size in values.yaml. So you need to request your storage provider.

  persistence:
    enabled: true
    ## A manually managed Persistent Volume and Claim
    ## Requires persistence.enabled: true
    ## If defined, PVC must be created manually before volume will be bound
    # existingClaim:
    ## influxdb data Persistent Volume Storage Class
    ## If defined, storageClassName: <storageClass>
    ## If set to "-", storageClassName: "", which disables dynamic provisioning
    ## If undefined (the default) or set to null, no storageClassName spec is
    ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
    ##   GKE, AWS & OpenStack)
    ##
    storageClass: "alicloud-disk-available"
    annotations: {}
    accessMode: ReadWriteOnce
    size: 25Gi

[MohamedShaj]

Okay,

Got it.

But for some requirement, we are making n/w share with meta and data and using AWS EFS means,

> `    persistence:
>       enabled: true
>       ## A manually managed Persistent Volume and Claim
>       ## Requires persistence.enabled: true
>       ## If defined, PVC must be created manually before volume will be bound
>       # existingClaim:
>       ## influxdb data Persistent Volume Storage Class
>       ## If defined, storageClassName: <storageClass>
>       ## If set to "-", storageClassName: "", which disables dynamic provisioning
>       ## If undefined (the default) or set to null, no storageClassName spec is
>       ##   set, choosing the default provisioner.  (gp2 on AWS, standard on
>       ##   GKE, AWS & OpenStack)
>       ##
>       storageClass: "efs-sc"
>       accessMode: ReadWriteMany
>       size: 10Gi  `
>       

EFS-SC is the efs storage class.
the above config should work right ?

[chengshiwen]

First, you need to check whether efs-sc exists by executing kubectl get sc, and then check whether the size meets the requirements. If the size is set too small, it may not meet the storage provider's requirements. And finally, test whether the cluster can work normally in k8s.