Deprecate legacy retries (read & write)

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Fixed
    • Priority: Unknown
    • 2.24.2
    • Affects Version/s: None
    • Component/s: Retryability
    • None
    • None
    • Ruby Drivers
    • Needed
    • Hide

      1. What would you like to communicate to the user about this feature - we deprecate our "legacy retry" machinery, and it will be removed in 3.0.
      2. Would you like the user to see examples of the syntax and/or executable code and its output - NO
      3. Which versions of the driver/connector does this apply to 2.24.2

      Show
      1. What would you like to communicate to the user about this feature - we deprecate our "legacy retry" machinery, and it will be removed in 3.0. 2. Would you like the user to see examples of the syntax and/or executable code and its output - NO 3. Which versions of the driver/connector does this apply to 2.24.2
    • None
    • None
    • None
    • None
    • None
    • None

      The "modern" retryable reads implementation was finished in April 2019, and retryable writes is from 2017. Do we still need to support the legacy retry implementations? I understand that there are some operations that may not be supported by the modern retry spec, which were supported under the legacy implementation, so even if we need to keep the implementation, can we deprecate and remove the options for people to select the legacy implementation? (:retry_reads and :retry_writes).

            Assignee:
            Dmitry Rybakov
            Reporter:
            Jamis Buck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: