[SERVER-75642] Fixing condition to mitigate some issues with the database metadata during a dropDatabase op Created: 04/Apr/23  Updated: 29/Oct/23  Resolved: 04/Apr/23

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

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

Issue Links:
Problem/Incident
is caused by SERVER-73391 Use recoverable critical section for ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-04-17
Participants:

 Description   

This issue was recently introduced in SERVER-73391. The problem is that this if-stmt should be executed when we are executing a pre 7.0 version of the dropDatabase coordinator and not when the coordinator is a 7.0 version or newer.

This special handling of the database metadata was introduced SERVER-73390 as a mitigation of some issues with the database metadata that should be addressed with the new implementation provided in SERVER-73391.



 Comments   
Comment by Githook User [ 04/Apr/23 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-75642 Fixing dropDb mitigation database metadata code
Branch: master
https://github.com/mongodb/mongo/commit/05794b52523f287f828a8fa692ac3f3ed6cd5dd1

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