[SERVER-45900] Range deleter task does not check for unsharded collection Created: 31/Jan/20  Updated: 29/Oct/23  Resolved: 12/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-02-10, Sharding 2020-02-24
Participants:
Linked BF Score: 25

 Description   

Before deleting a range the metadata is checked here and here in case the collection has been dropped and recreated, however it might've been recreated as a unsharded collection, which would hit an invariant when checking for the uuid so, before checking for the uuid, the range deleter should check if the collection is not sharded first.



 Comments   
Comment by Githook User [ 12/Feb/20 ]

Author:

{'name': 'Jack Mulrow', 'username': 'jsmulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-45900 Check for unsharded collection when submitting range deletion task
Branch: master
https://github.com/mongodb/mongo/commit/3e59bad319da75f2ad51a13ac3239bd21e74c41e

Generated at Thu Feb 08 05:09:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.