Startup of replicaset takes very long

MongoDB Percona Operator for MongoDB
1

Hello

I have replicas = 3 and during startup, why does one pod after the other get started?

Lets say 1 pod takes 30min (after a “forced” shutdown), then you have to wait 3x30min. Any other options?

Regards
John

2

Hey @jamoser .

why does one pod after the other get started

It is the default behaviour of a StatefulSet. It uses OrderedReady Pod Management.

It is possible to change it by setting .spec.podManagementPolicy. But:

  1. I’m not sure that it is safe for replica set. I will need to consult with our experts.
  2. I don’t see it being supported in the Operator right now (you can’t set this option in the custom resource).

But also I’m curious - why it takes 30min to start a single Pod? What is the main driver there?