-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.0.4, 4.1.6
-
Component/s: Sharding
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
If a source shard primary steps down during a movePrimary, it's possible that the MovePrimarySourceManager variable never gets cleared. If the same node steps up and retries to move the same database, it will cause an invariant.
We should clear the MovePrimarySourceManager variables for databases for which a shard is primary on step-up (somewhere around here. If we do so, we can guarantee a clean state for all attempted movePrimaries.