[SERVER-58240] Wait for range deletion timeout is too short for FSM tests Created: 02/Jul/21  Updated: 29/Oct/23  Resolved: 08/Jul/21

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

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

Issue Links:
Depends
Problem/Incident
is caused by SERVER-55429 Abort migration earlier when receiver... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2021-06-28, Sharding EMEA 2021-07-12
Participants:
Linked BF Score: 51

 Description   

SERVER-55429 added a timeout when waiting for range cleanups in the recipient of a migration, currently the default timeout is 10 seconds, which seems to be a very short period of time for the concurrency suites.

We could solve this by either ensure we have a script that automatically retry the migration (like for example network_error_and_txn_override.js) and adding the string "operation was interrupted" to the error message, or find a more suitable default value for this parameter.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 08/Jul/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-58240 Increase range deletion wait timeout on recipient for FSM workloads
Branch: master
https://github.com/mongodb/mongo/commit/e2eaf884bc260cc711b505a6c2ca5c6607b0ee3a

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