Client Backpressure: overload retry policy

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Retryability
    • None
    • Client Backpressure 2
    • Java Drivers
    • Needed
    • Hide
      Please wait until the ticket is done. Only then will we be able to provide you with the documentation changes needed.

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      Please wait until the ticket is done. Only then will we be able to provide you with the documentation changes needed. 1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • In Progress
    • None
    • 9
    • 3
    • 100
    • -66
    • None
    • Hide

      Engineer(s): Valentin Kovalenko
      2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team.

      • Timeline updates
        • See above.
      • Any risks/blockers/impediments?
        • The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former).
        • The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed.
      Show
      Engineer(s): Valentin Kovalenko 2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team. Timeline updates See above. What was accomplished since the last update? Continued reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . The PR has been actively updated. Reviewed the existing non-draft JAVA PRs done as part of Client Backpressure . JAVA-5950 Update Transactions Convenient API with exponential backoff on retries [JAVA-6033] ServerHeartbeatSucceededEvent is not fired for initial POLL monitoring #1856 What's the focus over the next two weeks? Continue reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . Continue reviewing the existing JAVA PRs done as part of Client Backpressure as needed. Finish JAVA-6025: Client Backpressure: design overload retry policy , provided that the relevant spec requirements are approved, merged, and there is enough time left within the two weeks to finish the design. Any risks/blockers/impediments? The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former). The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed.
    • Hide

      2026-01-07 - No confidence status provided
      Engineer(s): Valentin Kovalenko
      2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team.

      • Timeline updates
        • See above.
      • Any risks/blockers/impediments?
        • The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former).
        • The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed.

            • 2026-01-07 - No confidence status provided
              Engineer(s): Valentin Kovalenko
              2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team.

      • Timeline updates
        • See above.
      • Any risks/blockers/impediments?
        • The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former).
        • The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed.
      Show
      2026-01-07 - No confidence status provided Engineer(s): Valentin Kovalenko 2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team. Timeline updates See above. What was accomplished since the last update? Continued reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . The PR has been actively updated. Reviewed the existing non-draft JAVA PRs done as part of Client Backpressure . JAVA-5950 Update Transactions Convenient API with exponential backoff on retries [JAVA-6033] ServerHeartbeatSucceededEvent is not fired for initial POLL monitoring #1856 What's the focus over the next two weeks? Continue reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . Continue reviewing the existing JAVA PRs done as part of Client Backpressure as needed. Finish JAVA-6025: Client Backpressure: design overload retry policy , provided that the relevant spec requirements are approved, merged, and there is enough time left within the two weeks to finish the design. Any risks/blockers/impediments? The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former). The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed. 2026-01-07 - No confidence status provided Engineer(s): Valentin Kovalenko 2026-01-01: "End date", "Final Cost Estimate" will be updated some time later after re-evaluating them with the team. Timeline updates See above. What was accomplished since the last update? Continued reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . The PR has been actively updated. Reviewed the existing non-draft JAVA PRs done as part of Client Backpressure . JAVA-5950 Update Transactions Convenient API with exponential backoff on retries [JAVA-6033] ServerHeartbeatSucceededEvent is not fired for initial POLL monitoring #1856 What's the focus over the next two weeks? Continue reviewing DRIVERS-3239: Add exponential backoff to operation retry loop for server overloaded errors . Continue reviewing the existing JAVA PRs done as part of Client Backpressure as needed. Finish JAVA-6025: Client Backpressure: design overload retry policy , provided that the relevant spec requirements are approved, merged, and there is enough time left within the two weeks to finish the design. Any risks/blockers/impediments? The new estimates will be higher than our original estimates, both because of the scope changes and because of the changes in our understanding (though the latter can be seen a subset of the former). The new estimates are likely to be done without having the specification work completed, let alone having the Java driver design for the overload retry policy completed.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This epic exists solely for reporting the work done by valentin.kovalenko@mongodb.com; update: and slav.babanin@mongodb.com.

      Specification changes

      Scope

      The driver specification changes this epic should implement are a subset of those introduced by DRIVERS-3160 that is referred to as "New retry logic, with token bucket" in the "Backpressure Estimate" document. It is difficult to tell what tickets constitute that subset:

      Done so far / in progress, regardless of being in scope

      The last commit I checked at https://github.com/mongodb/specifications/commits/master/ is 0605523, the last PR I checked is #1876.

      Design

            Assignee:
            Valentin Kavalenka
            Reporter:
            Valentin Kavalenka
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              None
              None
              None