[SERVER-74694] cleanupOrphaned command may fail with "Range deleter service not up error" on step up Created: 08/Mar/23  Updated: 29/Oct/23  Resolved: 12/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 7.0.0-rc0, 6.2.1
Fix Version/s: 7.0.0-rc0, 7.1.0-rc0, 6.3.2

Type: Bug Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0, v6.3
Sprint: Sharding EMEA 2023-04-17
Participants:
Linked BF Score: 0

 Description   

The cleanupOrphaned command is not checking if the RangeDeleterService is fully initialized and it may hit the 'Range deleter service not up' error here if the RangeDeleterService not yet initialized due to a step up.



 Comments   
Comment by Githook User [ 20/Apr/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-74694 Wait for Range Deleter initialization on cleanupOrphaned command
Branch: v6.3
https://github.com/mongodb/mongo/commit/8ea73c100dc6de269d237d82bcd1174f752318ab

Comment by Githook User [ 13/Apr/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-74694 Wait for Range Deleter initialization on cleanupOrphaned command

(cherry picked from commit e5df567c4a0ad3f1dab1141d859e596bf8dd16fc)
Branch: v7.0
https://github.com/mongodb/mongo/commit/83bef763ffadec1f64a11b7dbbe5455613581aa4

Comment by Githook User [ 12/Apr/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-74694 Wait for Range Deleter initialization on cleanupOrphaned command
Branch: master
https://github.com/mongodb/mongo/commit/e5df567c4a0ad3f1dab1141d859e596bf8dd16fc

Generated at Thu Feb 08 06:28:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.