Hi Alex, AFAIK, the emptyDir[1] can be used directly as local disks, and emptyDir can be defined by referring to this pod template[2].
If you want to use local disks through PV, you can first create a statefulSet and mount the PV through volume claim templates[3], the example “Local Recovery Enabled TaskManager StatefulSet”[4] provided in the docs may be useful. [1] https://kubernetes.io/docs/concepts/storage/volumes/#emptydir [2] https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/pod-template/#pod-template [3] https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#volume-claim-templates [4] https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/#local-recovery-enabled-taskmanager-statefulset Best, Yanfei Alex Craig <acr...@kollective.com> 于2023年10月19日周四 02:57写道： > > The recommended practice for RocksDB usage is to have local disks accessible > to it. The Kubernetes Operator doesn’t have fields related to creating disks > for RocksDB to use. > > > > For instance, say I have maxParallelism=10 but parallelism=1. I have a > statically created PVC named “flink-rocksdb”. The first TaskManager spins up > and mounts this PVC. But successive ones fail to start because there is no > PVC for them to mount. > > > > Has anybody solved this? Seems like a big issue with using Flink in > Kubernetes…
