Remove the copy of users and roles during logical backup
General
Escalation
General
Escalation
Description
PBM currently copies the cluster users and roles into the temp collections admin.pbmRUsers and admin.pbmRRoles during the logical backups, and then waits for it to be replicated from the primary node to the secondary.
In scenarios where there is replication lag in the replica set, this can result in the error below.
2025-02-23T09:04:08Z I [node:27017] [backup/2025-02-23T08:59:11Z] mark RS as error `wait for tmp users and roles replication: run out of time`: <nil>
2025-02-23T09:04:08Z I [node:27017] [backup/2025-02-23T08:59:11Z] mark backup as error `wait for tmp users and roles replication: run out of time`: <nil>
2025-02-23T09:04:08Z E [node:27017] [backup/2025-02-23T08:59:11Z] backup: wait for tmp users and roles replication: run out of time
Remove the copy-and-replicate mechanism to reduce the chance of issues, if possible.
PBM currently copies the cluster users and roles into the temp collections admin.pbmRUsers and admin.pbmRRoles during the logical backups, and then waits for it to be replicated from the primary node to the secondary.
In scenarios where there is replication lag in the replica set, this can result in the error below.
2025-02-23T09:04:08Z I [node:27017] [backup/2025-02-23T08:59:11Z] mark RS as error `wait for tmp users and roles replication: run out of time`: <nil> 2025-02-23T09:04:08Z I [node:27017] [backup/2025-02-23T08:59:11Z] mark backup as error `wait for tmp users and roles replication: run out of time`: <nil> 2025-02-23T09:04:08Z E [node:27017] [backup/2025-02-23T08:59:11Z] backup: wait for tmp users and roles replication: run out of timeRemove the copy-and-replicate mechanism to reduce the chance of issues, if possible.