Resharding metrics output from the currentOp command should be reset when a new operation is started

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The following metrics should be reset when a new resharding operation is started:

          totalOperationTimeElapsedMillis: int64
          remainingOperationTimeEstimatedMillis: int64
      
          approxDocumentsToCopy: int64
          documentsCopied: int64
          approxBytesToCopy: int64
          bytesCopied: int64
          totalCopyTimeElapsedMillis: int64
      
          oplogEntriesFetched: int64
          oplogEntriesApplied: int64
          totalApplyTimeElapsedMillis: int64
      
          countWritesDuringCriticalSection: int64
          totalCriticalSectionTimeElapsedMillis: int64
      
          // Note that 0 corresponds to kUnused for these enum values and therefore
          // won’t be ambiguous when reset.
          coordinatorState: int32
          donorState: int32
          recipientState: int32
      

              Assignee:
              Kshitij Gupta (Inactive)
              Reporter:
              Lamont Nelson
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: