Hi Team,
We have an EKS (AWS) cluster with hybrid version 1.7.1 and there was a AMI upgrade performed recently and after this one of the Cassandra pod went into Pending state due to Availability Zone(AZ) issue later changed the AZ value in the PVC corresponding to that Cassandra pod then the pod came up into running state.
As we have four AZ’s available from (a-d) when the pvc is pointing to AZ(d) pod has not come up as soon as we changed the pvc AZ value from (d) to (a) it went into running state. But the thing here is ideally pod should come into running state right irrespective of AZ i.e., from a-d . The other two PVC’s are in AZ(b) which are running good.
Does anyone know what is the pattern/fashion of these AZ’s getting assigned to the PVC’s.
Thanks in advance.