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

ShardingStateRecovery::recover cleanup should not wait for replication

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.9, 3.3.10
    • Affects Version/s: 3.2.7, 3.3.9
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • Sharding 17 (07/15/16)

      Upon success the ShardingStateRecovery::recover call tries to cleanup the recovery document and uses majority write concern to do that. This method is called at the end of draining mode, but still under the global X lock and as a result it will never replicate and will stall leaving the draining mode.

      Instead, ShardingStateRecovery::recover should use local-only write concern.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: