[SERVER-67538] Multi-doc transactions should fail if on an old, incompatible snapshot Created: 27/Jun/22 Updated: 29/Oct/23 Resolved: 31/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0, 5.0.10, 6.1.0-rc1 |
| Fix Version/s: | 5.0.14, 6.0.2, 6.1.0-rc1, 6.2.0-rc0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Josef Ahmad | Assignee: | Josef Ahmad |
| 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 | |||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v6.1
|
|||||||||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Run this noPassthrough jstest.
|
|||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Execution Team 2022-07-25, Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-09-05 | |||||||||||||||||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 100 | |||||||||||||||||||||||||||||||||||||||||||
| Description |
|
In the following scenario:
Adding _indexCatalogEntry->isReady(opCtx) in _indexKeysOrWriteToSideTable resolves the issue: step 3 fails with SnapshotUnavailable, instead of silently progressing with an invalid, stale snapshot. |
| Comments |
| Comment by Githook User [ 28/Sep/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: Background: This patch introduces a check for the indices' minimum visible timestamp. (cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03) |
| Comment by Githook User [ 14/Sep/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: Background: This patch introduces a check for the indices' minimum visible timestamp. (cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03) |
| Comment by Githook User [ 07/Sep/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: Background: This patch introduces a check for the indices' minimum visible timestamp. (cherry picked from commit a4bd3ce3607d2c3020d7efa3501240ae4b1a1b03) |
| Comment by Githook User [ 31/Aug/22 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: Background: This patch introduces a check for the indices' minimum visible timestamp. |