Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38653

Don't allow stale MovePrimarySourceManager pointers to exist on DatabaseShardingStates on transition to primary.

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.4, 4.1.6
    • Component/s: Sharding
    • Labels:
      None
    • ALL

      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. 

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: