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

Remove UninterruptibleLockGuards in sharding code to allow interruptible lock acquisition

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • 3.7.3
    • Sharding
    • None
    • Sharding
    • Sharding 2019-02-11

    Description

      Since SERVER-32638, global and database locks can be interrupted when an OperationContext is killed and throw a DBException with an Interrupted error code. This includes all AutoGet helpers.

      The following places in the sharding code have temporary UninterruptibleLockGuard s to prevent crashing due to inadequate exception handling:

      MigrationSourceManager

      MovePrimarySourceManager

      CollectionRangeDeleter

       

       

       

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: