[SERVER-65584] Investigate if shard splits should be aborted when a concurrent reconfig is run Created: 13/Apr/22 Updated: 06/Dec/22 Resolved: 26/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Didier Nadeau | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Participants: |
| Description |
|
We should investigate if a shard split should be aborted if there's a concurrent reconfig. Once the correct behavior is agreed upon and implemented, a test for the various corner cases, based on `tenant_migration_concurrent_reconfig.js` should be created. N.B. It seems the desired behaviour would simply be to ensure the shard split fails cleanly (goes into aborted state, no data corruption/etc) when a reconfig occurs at various steps of the shard split. |
| Comments |
| Comment by Matt Broadstone [ 26/May/22 ] |
|
Confirmed with milkie@mongodb.com, siyuan.zhou@mongodb.com, and louisa.berger@mongodb.com that the automation agent would only ever perform a single reconfig on a replica set at a time. |