-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently, resharding recipients use the overall average oplog application rate to estimate 'remainingTimeMillis'. This can lead to a very inaccurate estimate for 'remainingTimeMillis' if the "apply" state is long and the oplog application rate is not steady. Using an exponential moving average can alleviate this since it applies more weight to the recent applying rate.
- is related to
-
SERVER-84769 Resharding remainingOpTime algorithm doesn't work with low elapsedTime
-
- Closed
-
- related to
-
SERVER-106058 Make resharding recipients estimate remaining time based on exponential moving average of the time it takes to fetch and apply oplog entries
-
- Closed
-