Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.4
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Execution Team 2020-02-24, Execution Team 2020-03-09
Linked BF Score:
50
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Maria van Keulen
Reporter:: Maria van Keulen
Participants:: Githook User, Maria van Keulen
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Feb 20 2020 09:32:58 PM UTC
Updated:: Oct 29 2023 10:11:58 PM UTC
Resolved:: Feb 28 2020 05:36:27 PM UTC
Confidence Status Last Update:: 21/Feb/20 8:38 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates