-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Catalog and Routing
-
ALL
In a failover scenario it might happen that a new primary steps up but it is not aware of the latest performed DDL operation because it has an old configTime . This can lead us to scenarios like the one described in BF-26346, in which we ended up installing an old filtering metadata.
- split to
-
SERVER-73389 Checkpoint vector clock in drop database coordinator
- Closed