Add diagnosability and supportability features for refining a shard key

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2019-08-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As described in the diagnosis/debuggability section of the design document, the following behavior should be added:

      1. Log to the config server primary’s main log timing stats at each phase of the transaction used to refine a collection’s shard key.
        • e.g. before and after updating the collection document, after updating each chunk, and after updating each zone range.
      2. Add change log writes at beginning and end of refining a shard key.

            Assignee:
            James Heppenstall (Inactive)
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: