Apply RetryableError label to idempotent operations that fail with retryable errors

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Scheduling
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The new "RetryableError" label introduced indicates that an operation can be retried, regardless of its content. This is a generalization of the existing "RetryableWriteError" label, which applies only to writes that include the proper retryability metadata.

      Currently, this label is only applied to error responses from ingress request rate limiting rejections, but we should extend this to other idempotent operations such as:

      • Non-getMore reads
      • Any operation that was rejected prior to doing any work that might have side effects (e.g. a getMore that didn't advance any server-side cursor state)

      It shouldn't be necessary to apply this label to error responses that already include the "RetryableWriteError" label.

              Assignee:
              Unassigned
              Reporter:
              Patrick Freed
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: