-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
It currently uses numRecipients to calculate this which will always include the recipient even if it won't copy data. We should re-think this metric and what useful information it's providing us and come up with something better.
- related to
-
SERVER-92979 Make resharding account for the number of recipients without chunks when calculating 'approxBytesToCopy' and 'approxDocumentsToCopy'
-
- Closed
-