[SERVER-84026] Ignore ConflictingOperationInProgress in random_moveChunk_update_shard_key_kill_sessions.js Created: 08/Dec/23 Updated: 02/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
See the linked BF for more details, but an update using the non internal transaction implementation that changes a document's shard key value and is retried on an Interruption error can fail with ConflictingOperationInProgress because a mongos already "started" tracking a transaction with the update's txnNumber. This test retries on interruption errors since it expects them, but in practice a driver won't retry on them, so a test only fix to ignore ConflictingOperationInProgress seems appropriate. |