-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2020-02-24, Execution Team 2020-03-09
-
50
Presently, collections created inside multi-document transactions are each individually registered during transaction commit. However, if the transaction gets aborted midway through the commit, those previously registered collections need to be rolled back.
In order to guarantee transaction isolation, the newly-registered collections should only be visible once the entire transaction has committed.
One potential solution to achieve this visibility handling is by preventing reads on the existing minVisibleTimestamp.
- is depended on by
-
SERVER-45060 Operations can use a Collection without having a storage snapshot where that collection is visible
- Closed
- is related to
-
SERVER-45060 Operations can use a Collection without having a storage snapshot where that collection is visible
- Closed
-
SERVER-46253 Rolling back a partially-committed collection creation transaction can cause catalog inconsistencies
- Closed
- related to
-
SERVER-46761 getAllDbNames can return incomplete list of dbNames
- Closed