Update the what field in the changelog entries for shard draining operations to ensure distinct and accurate labelling

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The stopShardDraining command should set what: stopShardDraining instead of the current what: removeShard.stopShardDraining.

      To avoid ambiguity the changelog entries for startShardDraining and removeShard (when initiating shardDraining) must use distinct what values.
      Specifically:

      Remove the logChange call from the checkPreconditionsAndStartDrain function.

      Set what: removeShard.start for the removeShard function.

      Set what: startShardDraining for the startShardDraining command.

            Assignee:
            Unassigned
            Reporter:
            Laura Mestres Torres (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: