It’s more a Kubernetes question …
Assuming you run the MongoDB cluster on multiple nodes. Now there are a lot of writes which all go to the master/writer pod of the Statefulset. In some cases Kubernetes might try the reschedule the “writer pod” to a different node, if it creates too much load on the node. The pod gets rescheduled and the “Writer” is moved to another pod - but the problem arises again, rescheduling … and so forth until ALL of the pods got rescheduled. Since the startup of each pod/mongdb takes some time, at some point the whole cluster is NOT AVAILABLE any more.
Is there an elegant and RECOMMENDED way to make the pods sticky so that the other pods on the node get rescheduled.