Overly strict retry predicate in ContinuousAddRemoveShard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The retry predicate for adding/removing config shards is intended to allow connection errors as retryable. However, the check for connection errors requires an OperationFailed error code (96) and does not match ConnectionClosedByPeer error codes (515). As a result, the add/remove shard thread fails instead of retrying the operation.

            Assignee:
            Unassigned
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: