[SERVER-34637] Prevent race condition with database drop in database_versioning_safe_secondary_reads test Created: 24/Apr/18  Updated: 29/Oct/23  Resolved: 24/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.5
Fix Version/s: 4.0.0-rc0

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2018-05-07
Participants:
Linked BF Score: 16

 Description   

In the database_versioning_safe_secondary_reads test, we drop a database then check if all of the nodes reflect that change. It's possible to run the check before the change replicates to al nodes. To change, we must await replication after the drop has been performed.



 Comments   
Comment by Githook User [ 24/Apr/18 ]

Author:

{'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake', 'name': 'Blake Oler'}

Message: SERVER-34637 Prevent race condition with database drop in database_versioning_safe_secondary_reads test
Branch: master
https://github.com/mongodb/mongo/commit/3d5b853e47fc1011a3191f3522148987de65b6b0

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