[SERVER-27921] Add 'waitForDelete' functionality to CollectionRangeDeleter Created: 06/Feb/17  Updated: 06/Dec/17  Resolved: 20/Apr/17

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Nathan Myers
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-17751 Make cleanupOrphaned cmd interruptible Closed
Duplicate
is duplicated by SERVER-19226 RangeDeleter should stop worker threa... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-02-13, Sharding 2017-03-06, Sharding 2017-03-27, Sharding 2017-04-17, Sharding 2017-05-08
Participants:

 Description   

The waitForDelete option of moveChunk ensures that before the command returns, all orphaned documents would be deleted. This is necessary mostly for synchronization in tests, but also used by customers occasionally.

When fixing the range deleter, we should preserve this functionality as much as we can by exposing some way to block waiting until a particular range has been removed from the rangesToClean list.



 Comments   
Comment by Nathan Myers [ 20/Apr/17 ]

New function is CollectionShardingState::waitForClean that waits for completion of previous deletion requests. waitForClean returns after all outstanding deletion requests that include any part of the requested range have been completed, or failed.

Comment by Githook User [ 20/Apr/17 ]

Author:

{u'username': u'nathan-myers-mongo', u'name': u'Nathan Myers', u'email': u'nathan.myers@10gen.com'}

Message: SERVER-27921 New Range Deleter
Branch: master
https://github.com/mongodb/mongo/commit/c192a1b9b1e223f8075ab5ce72dde372467f9650

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