You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imaging I have 3 NVMEs and I'd like to deploy 3 database replicas on the node, where the data was replicated internally by the DBMS, naturally the 3 PVs should be provisioned on each NVME.
So are there any ways to do anti-affinity like this? Maybe a simple round-robin policy (instead of random policy) to choose the underlying path?
The text was updated successfully, but these errors were encountered:
ccll
changed the title
[Question] Spread PVC over all host paths
[Question] PV anti-affinity over all host paths
Jul 4, 2022
Hello~ @derekbit Is there a plan to solve this issue?
I also have the same problem. Currently, multiple disks correspond to multiple mountpoints, which are added to the configmaps. However, the local-path-provisioner randomly selects a path. The storageclass can only choose one of the paths. It is not very convenient for the scenario of multiple disks and multiple paths.
The doc says:
Imaging I have 3 NVMEs and I'd like to deploy 3 database replicas on the node, where the data was replicated internally by the DBMS, naturally the 3 PVs should be provisioned on each NVME.
So are there any ways to do anti-affinity like this? Maybe a simple round-robin policy (instead of random policy) to choose the underlying path?
The text was updated successfully, but these errors were encountered: