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

ShardingStateRecovery::recover cleanup should not wait for replication

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.7, 3.3.9
    • Fix Version/s: 3.2.9, 3.3.10
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding 17 (07/15/16)

      Description

      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.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: