Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14204

Investigate changes in SERVER-53842: Count the number of resharding attempts in resharding metrics

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Mar2 - Mar9

      Description

      Description

      Downstream Change Summary

      This ticket adds a new metric, countReshardingOperations, to track the number of attempted resharding operations, and makes the following changes:

      • successfulOperations to countReshardingSuccessful.
      • failedOperations to countReshardingFailures.
      • canceledOperations to countReshardingCanceled.

      Description of Linked Ticket

      Currently, we only include the number of successful, failed, and canceled operations in resharding metrics. We need a new counter that represents the number of attempted resharding operations, and is updated along with new resharding operations.

      This ticket should also fix the naming for successfulOperations, failedOperations, and canceledOperations to match the design document.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jason.price Jason Price
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 weeks, 6 days ago
                Date of 1st Reply: