Hi @Reab_AB,
It sounds like you are experiencing an issue similar to replSetReconfig force generates too high version number.
It is expected that a force reconfiguration will increment the replica set config version but
that should be in the order of 10s or 100s of thousands, not millions. Replica set members compare the version number and replica set name to determine if their configuration is stale, so you cannot force an older version number.
Can you provide more details on your environment:
- specific version of MongoDB server
- O/S version
- current version of the replica set config
- steps to reproduce (for example, was this a single force reconfig or the result of several)
Thanks,
Stennie