[SERVER-39840] Allow TransactionParticipant to "restart" from state::kNone in order to upgrade retryable write to transaction Created: 26/Feb/19 Updated: 29/Oct/23 Resolved: 29/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-03-25, Sharding 2019-04-08 |
| Participants: |
| Description |
|
In order to allow updating a document's shard key value when the write is not part of a multi-stmt transaction, the TransactionParticipant state machine needs to be allowed to restart from state::kNone. This is so that we can re-use the session and transaction number for both the original update and the internal transaction started by MongoS. |
| Comments |
| Comment by Githook User [ 29/Mar/19 ] |
|
Author: {'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}Message: |