[SERVER-45026] updates_to_rangedeletions_collection_trigger_range_deletions.js should wait for deletions to complete before inserting orphans Created: 09/Dec/19  Updated: 29/Oct/23  Resolved: 10/Dec/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.3.2
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Alexander Taskov (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Service Arch 2019-12-16
Participants:
Linked BF Score: 16

 Description   

This test creates two shards with a chunk in each one. It then inserts documents to both and inserts some orphans directly to one of the shards. However, the initial moveChunk command will queue the chunk for deletion on the first shard asynchronously and may not run until after the orphans are inserted causing them to be deleted too early. 

The test should use _waitForDelete in the moveChunk call. We should also review all of the related range deletion tests to see if this fix is needed there as well.



 Comments   
Comment by Githook User [ 10/Dec/19 ]

Author:

{'email': 'alex.taskov@mongodb.com', 'name': 'Alex Taskov', 'username': 'alextaskov'}

Message: SERVER-45026 updates_to_rangedeletions_collection_trigger_range_deletions.js should wait for deletions to complete before inserting orphans
Branch: master
https://github.com/mongodb/mongo/commit/29574ea94aa09e011189aab880a4494cf0ea455f

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