-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 6.0.3, 6.1.0-rc4, 6.2.0-rc2
-
Component/s: None
-
None
-
Fully Compatible
-
v6.2, v6.1, v6.0
-
Sharding EMEA 2022-12-12
-
153
SERVER-71085 introduced new logic in release 6.3 that may cause CollectionCatalog::lookupView() to be invoked within the context of a collName.drop() execution (and consecutively, to raise an InvalidViewDefinition exception in case corrupted data are detected).
This behaviour goes against what was implemented in SERVER-42373 - and this is why SERVER-71085 also introduced a try/catch clause to not propagate such error (and make the needed deductions when it is detected).
For collName.drop() to maintain the semantics established by SERVER-42373 in multiversion cluster, the try/catch clause needs to also be backported to previous release branches.
- is caused by
-
SERVER-71085 DropCollectionCoordinator should only report a single drop event through the Primary Shard oplog
- Closed