Search code examples
cassandrakuberneteskubernetes-pod

Cassandra on Kubernetes podManagementPolicy - OrderedReady vs. Parallel


Every article I've seen on the internet about running a Cassandra cluster on Kubernetes were either omitting the podManagementPolicy field or setting it to OrderedReady which is essentially the same thing because it is the default value.

I was wondering if it is possible to use podManagementPolicy: Parallel to speed up the process of synchronizing when multiple nodes of the Cassandra cluster restart.


Solution

  • As far as I know, this is a bad idea. I tried it and got the last node going into CrashLoopBackoff. It seems like the reason is that joining nodes crash if they see another node is trying to join at the same time.

    podManagementPolicy: OrderedReady should be the way to go.