-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ClusterScalability 26Oct-9Nov, ClusterScalability 9Nov-23Nov
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Add a TestData flag (see configShard) that makes an additional resharding operation start in the background concurrently (_withOperationInBackground). It should be on a distinct namespace but on the same donors and recipient shards. it should complete before any consistency checks run. this should be feature flag gated for now, and not run in suites with older binaries. the background resharding should have its own state instead of reusing _ns, _tempNs, etc and shouldn't interfere with cluster-wide asserts. an opt-out tag should also be added for tests that this isn't viable for ($currentOp, localReshardingOperations, unscoped config.reshardingOperations, abortReshardCollection, killOp). Similarly, tests with shard-wide failpoints shouldn't run concurrent reshardings. This ticket depends on SERVER-138367.
- depends on
-
SERVER-138367 Add namespace to ReshardingTest fixture coordinator failpoints
-
- Backlog
-
- is depended on by
-
SERVER-138369 Add concurrent_resharding matrix suites for ReshardingTest suites
-
- Backlog
-