-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
Fully Compatible
-
v9.0, v8.0
-
ClusterScalability 31Aug-14Sep, ClusterScalability 14Sep-28Sep
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Similar to resharding.
Similar to resharding, we want the log to only appear once per movechunk execution (no duplicate logs when movechunk is re-run during recovery). And potentially capture all errors encountered during moveChunk (should at least have covered cases when the countDonorMoveChunkAborted stat is incremented).
Note that in the resharding log, all the details are jammed into the "info" field. We also want to do something similar for moveChunk so it would be easy to setup the log ingestion rule and capture the "info" field.
Some minimum info to include: error code, success/fail
Some nice to have to include: breakdown of time spent per phase (like in changelog), docs cloned, xferMods count, txnId copied, etc.
- is related to
-
SERVER-135164 Expand the logging in chunk migration
-
- Needs Scheduling
-