[SERVER-50545] Retry on ConflictingOperationInProgress in index_operations_abort_concurrent_outgoing_migrations.js Created: 26/Aug/20 Updated: 29/Oct/23 Resolved: 04/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Sharding 2020-09-07 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 39 | ||||||||
| Description |
|
jstests/sharding/index_operations_abort_concurrent_outgoing_migrations.js runs a migration after an earlier one with the same donor and recipient is aborted because of an index operation, which is susceptible to failing with ConflictingOperationInProgress if the following sequence occurs:
Eventually the recipient shard should clean up state from the failed migration and allow new migrations involving it to succeed, so to handle this, the test should retry its migrations on ConflictingOperationInProgress. |
| Comments |
| Comment by Githook User [ 17/Sep/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: (cherry picked from commit 49153d63a1a19c8dbbd186a8542609b2e7f41d13) |
| Comment by Jack Mulrow [ 04/Sep/20 ] |
|
The changes from |
| Comment by Githook User [ 04/Sep/20 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |