[SERVER-40655] Test that a retryable write that changes the shard key behaves correctly with conflicting writes Created: 15/Apr/19 Updated: 29/Oct/23 Resolved: 18/Apr/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: | Janna Golden |
| 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-04-22 |
| Participants: |
| Description |
|
We should test the following scenarios: 1. If a concurrent update modifies the same document such that the original update query will still match, we do not lose the conflicting write. |
| Comments |
| Comment by Githook User [ 18/Apr/19 ] |
|
Author: {'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: |