[SERVER-56311] Limit atomic_rename_collection.js to check particular databases it uses. Created: 23/Apr/21  Updated: 29/Oct/23  Resolved: 27/Apr/21

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

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.9
Sprint: Repl 2021-05-03
Participants:
Linked BF Score: 33

 Description   

This test assumes it's the only thing creating oplog entries in the system, which is no longer true with tenant migration creating indexes on startup (but after the system is live). It seems unreasonable to restrict background services to not do that, so better to limit the test.



 Comments   
Comment by Githook User [ 27/Apr/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-56311 Limit atomic_rename_collection.js to check particular databases it uses.
Branch: master
https://github.com/mongodb/mongo/commit/13222cc37885b06ae4627f57567758d0a2c4d50b

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