[SERVER-65016] Remove range deletions as part of `dropCollection` Created: 29/Mar/22 Updated: 29/Oct/23 Resolved: 23/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding EMEA 2022-10-03 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When a sharded collection is dropped, the range-deleter is lazily discovering that some range deletions may refer an older incarnation of such collection (dropped or dropped and recreated).
While de-queueing already scheduled range deletion tasks that may not be trivial, a simple optimization could be to delete persistent range deletion task documents so that:
This change is safe because the range-releter is already handling the absence of a document for a scheduled range deletion. |
| Comments |
| Comment by Githook User [ 27/Sep/22 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |
| Comment by Githook User [ 23/Sep/22 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |
| Comment by Cris Insignares Cuello [ 26/May/22 ] |
|
Removed from QWs and added to PM-2849 |