Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- resharding-critical-section-timeout
- resharding-improvements

Assigned Teams:

Cluster Scalability
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
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

Assignee:: Unassigned
Reporter:: Cheahuychou Mao
Participants:: Cheahuychou Mao
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jul 26 2024 07:10:49 PM UTC
Updated:: Jun 09 2025 03:10:04 PM UTC
Resolved:: Feb 24 2025 09:17:47 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates