[SERVER-29368] Abort waiting on range deletion fails dassert Created: 25/May/17  Updated: 30/Oct/23  Resolved: 26/May/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.5.8

Type: Bug Priority: Major - P3
Reporter: Nathan Myers Assignee: Nathan Myers
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-05-29, Sharding 2017-06-19
Participants:

 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



 Comments   
Comment by Githook User [ 26/May/17 ]

Author:

{u'username': u'ncm', u'name': u'Nathan Myers', u'email': u'ncm@cantrip.org'}

Message: SERVER-29368 Clean up on interrupted wait for range deletion
Branch: master
https://github.com/mongodb/mongo/commit/4b88bf79dc47cbdfd74a11605cc5ee1c61e379f8

Generated at Thu Feb 08 04:20:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.