[SERVER-36957] Retry DDL operations when encountering BackgroundOperationInProgressForNamespace in a concurrency test Created: 31/Aug/18  Updated: 29/Oct/23  Resolved: 22/Feb/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Task Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: stm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2019-02-25
Participants:
Linked BF Score: 29

 Description   

It's possible for a secondary to step up as primary and subsequently receive a dropIndexes or collmod command while a background index (started during steady state oplog application) is still in progress. We should add a retry override to handle this scenario.



 Comments   
Comment by Githook User [ 22/Feb/19 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-36957 Retry DDL operations when encountering BackgroundOperationInProgress
Branch: master
https://github.com/mongodb/mongo/commit/95ded0aae6314c3e4cc18fa45a4d20cbadba19d6

Comment by Githook User [ 22/Feb/19 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-36957 Fix Date.prototype.tojson()
Branch: master
https://github.com/mongodb/mongo/commit/af5ab190304b60cc04d234311365f37f08b99e1d

Generated at Thu Feb 08 04:44:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.