[SERVER-53372] Remove reshardingTempInterruptBeforeOplogApplication server parameter so reshardCollection runs to completion Created: 15/Dec/20 Updated: 29/Oct/23 Resolved: 24/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Sharding 2020-12-28 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||
| Description |
|
The --setParameter reshardingTempInterruptBeforeOplogApplication=false was introduce to enable the ReshardingTest fixture and the resharding fuzzer to exercise the entirety of resharding's data replication while the lifecycle portions of the reshardCollection command were still being worked on. The reshardingTempInterruptBeforeOplogApplication should be removed once the remaining work on the lifecycle are completed. This requires updating existing JavaScript tests for resharding to potentially change their expectations for when _configsvrReshardCollection currently returns. |
| Comments |
| Comment by Max Hirschhorn [ 24/Dec/20 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: |