[SERVER-56915] Disable delete_range_deletion_tasks_on_stepup_after_drop_collection.js on stepdown suites Created: 13/May/21  Updated: 29/Oct/23  Resolved: 14/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2021-05-17
Participants:
Linked BF Score: 137

 Description   

This test uses fail points to artificially block refreshes. In case of CSRS stepdown, a migration can get aborted calling for a cleanup that can fail half-way since the shard primary can also step down . This can result in a deadlock on migration resume because the test could fail before re-enabling refreshes.

Check BF-20591 for the full explanation.



 Comments   
Comment by Githook User [ 13/May/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-56915 Disable delete_range_deletion_tasks_on_stepup_after_drop_collection.js on stepdown suites
Branch: master
https://github.com/mongodb/mongo/commit/5e3fb35984243f1148c672acbc8a9cc4760f474c

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