-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
Cluster Scalability 2024-11-11, Cluster Scalability 2024-12-23, Cluster Scalability 2025-01-20, Cluster Scalability 2025-03-03
-
200
Currently the recipient transition to cloning is using refresh. This should be through the coordinator sending an explicit command.
This adds:
- feature flag
- start clone command
- coordinator side sending command
- recipient side handling command and responding
- modify existing unit tests to test persistence and state transitions through step up/step down.
- unit tested coordinator sending cmd, recipient fulfilling promise function, and no transition to cloning on refresh if the feature flag is enabled.
- is duplicated by
-
SERVER-96285 Create feature flag
-
- Closed
-
- is related to
-
SERVER-101283 Investigate whether reshardNoRefresh unit tests randomness can be eliminated
-
- Closed
-