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

Abort waiting on range deletion fails dassert

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.8
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2017-05-29, Sharding 2017-06-19

      Description

      When a command is waiting for notification that a range deletion has completed, and the wait is interrupted, the waitStatus call throws an exception and the destructor for the notification does not see the required state, and dasserts out.

      CollectionRangeDeleter::DeleteNotification::waitStatus should catch exceptions and re-throw after satisfying invariants necessary for safe destruction.

      Failure in parallel.js:
      https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_debug_asan_sharding_693c380bdd4af37c72a554af7b86439f7020d03e_17_05_24_22_15_57

        Attachments

          Activity

            People

            Assignee:
            nathan.myers Nathan Myers
            Reporter:
            nathan.myers Nathan Myers
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: