[SERVER-70248] Race in ShouldBeSafeToRetryOnStepDown test can lead to hang Created: 05/Oct/22  Updated: 29/Oct/23  Resolved: 06/Oct/22

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-70247 SyncTransactionWithRetries used with ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2022-10-17
Participants:
Linked BF Score: 14

 Description   

Currently, the global index cloner doesn't skip the clone phase after it steps up even if the current step is already beyond it. This is mostly harmless as it will end up doing no writes because all documents that needs to be fetched are already cloned. However, this can still cause it to start a transaction when reading the skip id collection. If the cleanup gets called while that transaction is still running, it will trigger SERVER-70247 and cause the transaction to stay alive even after the cloner finished. This will then cause the test to hang because the fixture will try to acquire MODE_X during destruction.



 Comments   
Comment by Githook User [ 06/Oct/22 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-70248 Race in ShouldBeSafeToRetryOnStepDown test can lead to hang
Branch: master
https://github.com/mongodb/mongo/commit/b74adb6c6b5efb23814d1cf0234088f337ea4861

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