[SERVER-76807] The split prepared transaction mechanism causes opTimes for non-retryable internal transactions to get added to the session migration new opTime buffer Created: 03/May/23 Updated: 29/Oct/23 Resolved: 17/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||
| Sprint: | Sharding NYC 2023-05-29 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 135 | ||||||||||||||||
| Description |
|
Non-retryable internal transactions refer to internal transactions started internally to execute some write for a client with retryWrite: false session. Such transactions always have session id of the form (id, uid, txnUUID) where where id is the id of the client session and txnUUID is an internally generated UUID. Such session ids are exclusively used to run internal transactions so they can never be used to run retryable writes. As such, they are not migrated during chunk migration. Currently, this is how they are excluded from session migration:
However, there have been some recent changes that can cause the the opTime for a non-retryable write internal transaction to end up in the new opTime buffer:
BF-28542 contains an example of how issue this manifests. As a quick fix, |
| Comments |
| Comment by Githook User [ 17/May/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |
| Comment by Githook User [ 16/May/23 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |