Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- resharding-improvements

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
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, the ReshardingRecipientService doesn't persist the 'approxDocumentsToCopy' and 'approxBytesToCopy' metrics in the recipient state document when it gets the cloning details from the coordinator (it only persists the 'cloneTimestamp'). The recipient state document is used for restoring the 'approxDocumentsToCopy' and 'approxBytesToCopy' metrics so currently 'approxDocumentsToCopy' and 'approxBytesToCopy' metrics are lost after failover.

is related to

SERVER-67650 Resharding recipient can return remainingOperationTimeEstimatedSecs=0 when the oplog applier hasn't caught up with the oplog fetcher

Closed

related to

SERVER-92979 Make resharding account for the number of recipients without chunks when calculating 'approxBytesToCopy' and 'approxDocumentsToCopy'

Closed

Assignee:: Cheahuychou Mao
Reporter:: Cheahuychou Mao
Participants:: Cheahuychou Mao, Githook User
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jul 29 2024 04:07:11 PM UTC
Updated:: Oct 17 2024 08:57:48 PM UTC
Resolved:: Oct 17 2024 08:57:48 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates