Loading...
Loading...
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.
xgen-internal-githook commented on Tue, 30 Jan 2024 12:33:09 +0000: 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
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.