[SERVER-84586] Catch staleConfig errors in kill_rooted_or.js Created: 05/Jan/24  Updated: 30/Jan/24  Resolved: 30/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc2

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Robert Sander
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-80372 Make implicit collection creation cal... Closed
Assigned Teams:
Catalog and Routing
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: CAR Team 2024-02-05
Participants:
Linked BF Score: 5
Story Points: 1

 Description   

The kill_rooted_or.js test is running concurrent dropCollection and index modification commands. This test is already handling certain errors that can be bubbled up to the user when a command fails due to the collection being concurrently dropped.

With the introduction of SERVER-80372, though, the probability of hitting a staleConfig error due to concurrent dropCollection has increased. This is because there is a longer period of time between the implicit creation of the collection and the creation of the index, making it more likely that a collection drop can start and grab the critical section while a createIndex is running.

This ticket is to add StaleConfig to the list of accepted errors due to the collection being dropped.



 Comments   
Comment by Githook User [ 30/Jan/24 ]

Author:

{'name': 'Robert Sander', 'email': 'robert.sander@mongodb.com', 'username': 'robsndr'}

Message: SERVER-84586 Catch staleConfig errors in kill_rooted_or.js (#18411)

GitOrigin-RevId: 6de93d073291956f7632879f52a0bea4693e3eb8
Branch: master
https://github.com/mongodb/mongo/commit/4605f710dcce5050d349736b2f6208e4a8a5ad05

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