[SERVER-50532] Cannot require that database exists when applying 'dropDatabase' oplog entry Created: 25/Aug/20  Updated: 29/Oct/23  Resolved: 23/Sep/20

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

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:
Related
is related to SERVER-46550 Enabling sharding creates a database ... Closed
is related to SERVER-21700 Do not relax constraints during stead... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-09-07, Repl 2020-09-21, Repl 2020-10-05
Participants:

 Description   

A 'database' in mongodb is an ephemeral entity; there are normal cases when we might apply a 'dropDatabase' entry when the database does not exist. (One such is if all collections are dropped, then the node restarts, then the database is dropped.) So we cannot assert that it does.



 Comments   
Comment by Githook User [ 23/Sep/20 ]

Author:

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

Message: SERVER-50532 Cannot require that database exists when applying 'dropDatabase' oplog entry
Branch: master
https://github.com/mongodb/mongo/commit/fbcda84ec973644a995127bc23d0d94392f3cbb1

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