Can't reduce replicaset size with delete psmdb and cluster re-creation
General
Escalation
General
Escalation
Description
Percona Kubernetes Operator for PSMDB removes all pods at once:
after deleting psmdb resource, the user can reduce replicaset size down to 1 & allowUnsafeConfigurations: true. As a result the cluster can't transit to the PRIMARY state.
The problem could be reproduced with both replicaset-only and sharded configuration.
Suggested fix: always start with the "before shutdown" number of nodes or terminate replica set nodes one by one.
Percona Kubernetes Operator for PSMDB removes all pods at once:
after deleting psmdb resource, the user can reduce replicaset size down to 1 & allowUnsafeConfigurations: true.
As a result the cluster can't transit to the PRIMARY state.
The problem could be reproduced with both replicaset-only and sharded configuration.
Suggested fix:
always start with the "before shutdown" number of nodes or terminate replica set nodes one by one.