-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v6.2, v6.0, v5.0
-
Sharding EMEA 2023-02-06
-
20
In order to mitigate the possibility of the defected interleaving described in SERVER-70600, in case the database already exists we now enforce a clean-up for the primary and secondaries of the related database info (including the dbVersion) before passing to the second phase and flush the cache.
However, there is still a small chance for the primary to recover the dbVersion if there is an stepdown during the execution of the 1st phase, as described in SERVER-70600. Therefore SERVER-70600 won't be completely fixed until we will introduce the Recoverable critical section (SERVER-73391)
- split from
-
SERVER-70600 dropDatabase DDL operation might complete with the old primary shard still believing that is the primary
- Closed