[SERVER-72608] Use minValid instead of minVisible when checking secondary namespaces Created: 06/Jan/23 Updated: 29/Oct/23 Resolved: 19/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Execution Team 2023-01-23 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Secondary namespaces should not throw SnapshotUnavailable either. See usages of assertAllNamespacesAreCompatibleForReadTimestamp in the PIT lookup code path. |
| Comments |
| Comment by Githook User [ 19/Jan/23 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 09/Jan/23 ] |
|
Looks like the code that can throw SnapshotUnavailable is here, and minValid means this _minValidSnapshot . IIUC. I presume we can create Collection instances for reads all the way back in time to a collection's minValidSnapshot timestamp now, so instead of fetching the minVisible, which reflects the last DDL op, here, we should fetch the minValidSnapshot. |