[SERVER-64207] Too low of 'receiveChunkWaitForRangeDeleterTimeoutMS' value for migration_fails_if_exists_in_rangedeletions.js Created: 04/Mar/22  Updated: 29/Oct/23  Resolved: 01/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: 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 2022-04-04
Participants:
Linked BF Score: 33

 Description   

The default receiveChunkWaitForRangeDeleterTimeoutMS value of 10 seconds is too low for migration_fails_if_exists_in_rangedeletions.js.

Specifically, the test kicks-off migration which will block on range deletion here and then waits for 5 seconds before it turns off the failpoint. By then, 5 seconds have already passed, so only 5 more seconds are left for the range deletion to actually complete.

We should increase it to at least 30 seconds for this whole test.

Also, looking at other tests, which set the suspendRangeDeletion failpoint, it looks like:

  • cleanup_orphaned_with_resumable_range_deleter.js
  • disable_resumable_range_deleter.js

May also be candidates in order to make them more robust.



 Comments   
Comment by Githook User [ 01/Apr/22 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-64207 Too low of 'receiveChunkWaitForRangeDeleterTimeoutMS' value for migration_fails_if_exists_in_rangedeletions.js
Branch: master
https://github.com/mongodb/mongo/commit/4c7f60204736dea74792bcd85f4da816a2fa94cc

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