Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-102867

Audit status returned from resharding coordinator after fail over

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On step up, if the status is aborted we return a generic status of {ReshardCollectionAborted, "aborted"} instead of the original status.

      We fixed the log line to log the original status in SERVER-73897 but we still pass along the generic status instead of the original.

      We should audit and refactor our exception handling in the resharding coordinator service to provide consistent behavior and proper status / exception handling.

            Assignee:
            Unassigned Unassigned
            Reporter:
            ben.gawel@mongodb.com Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None