[SERVER-46241] Ensure minVisibleSnapshots of collections created in multi-document transactions are appropriately set by the time they are visible in the catalog Created: 18/Feb/20 Updated: 29/Oct/23 Resolved: 02/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.5 |
| 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Execution Team 2020-03-09 |
| Participants: |
| Description |
|
When a collection gets created, it gets registered as part of the collection catalog during recovery unit commit. Its corresponding indexes have their minVisibleTimestamp set in a separate onCommit handler. Additionally, we set the minVisibleSnapshot of the newly-created collection to be a potentially null timestamp, before setting it again through creation of the _id index. |
| Comments |
| Comment by Githook User [ 02/Mar/20 ] |
|
Author: {'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria@mongodb.com'}Message: This patch specifically addresses collections created inside multi- |
| Comment by Louis Williams [ 26/Feb/20 ] |
|
Confirm whether this fix also fixes |
| Comment by Maria van Keulen [ 24/Feb/20 ] |
|
We should also consider the case in which a new index is created on an empty collection created earlier in the same transaction. |