[SERVER-40475] Migrate info that retryable write has turned into transaction during session migration Created: 04/Apr/19 Updated: 29/Oct/23 Resolved: 02/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2019-04-22, Sharding 2019-05-06 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 36 | ||||||||||||||||
| Description |
|
Since we will turn a retryable write into a transaction when an update to the shard key is sent as a retryable write, we need to migrate some info during session migration about this write. That way, if the chunk that owned the original document moves, an attempted retry will fail. In order to do this, we will need to add some extra field to config.transactions to indicate that the retryable write turned into a transaction. |
| Comments |
| Comment by Githook User [ 03/May/19 ] |
|
Author: {'email': 'golden.janna@gmail.com', 'name': 'jannaerin', 'username': 'jannaerin'}Message: |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'email': 'matthew.saltz@mongodb.com', 'name': 'Matthew Saltz', 'username': 'saltzm'}Message: |