-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
ALL
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