[SERVER-46285] Collections should not be visible in CollectionCatalog lookups until storage transaction commit Created: 20/Feb/20 Updated: 29/Oct/23 Resolved: 28/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2020-02-24, Execution Team 2020-03-09 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 28/Feb/20 ] |
|
Author: {'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria@mongodb.com'}Message: |
| Comment by Maria van Keulen [ 26/Feb/20 ] |
|
CC louis.williams I will confirm whether this addresses |