Client Backpressure

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Done
    • Priority: Major - P3
    • 2.24.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Client Backpressure Spec
    • Ruby Drivers
    • Needed
    • Hide
      1. What would you like to communicate to the user about this feature?
      Intelligent Workload Management support has been introduced at the client layer.
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      Yes, check RUBY-3798
      3. Which versions of the driver/connector does this apply to?
      2.24+
      Show
      1. What would you like to communicate to the user about this feature? Intelligent Workload Management support has been introduced at the client layer. 2. Would you like the user to see examples of the syntax and/or executable code and its output? Yes, check RUBY-3798 3. Which versions of the driver/connector does this apply to? 2.24+
    • Done
    • 7
    • 8
    • 🔵 Done
    • Hide

      Engineer(s): Dmitry Rybakov

      What was accomplished since the last update?

      • Implemented backpressure logic for retried and transactions, including the token bucket.

      What's the focus over the next two weeks?

      • Finalize the implementation according to the rollout plan.

      Any risks/blockers/impediments?

      • N/A 

       

      Show
      Engineer(s): Dmitry Rybakov What was accomplished since the last update? Implemented backpressure logic for retried and transactions, including the token bucket. What's the focus over the next two weeks? Finalize the implementation according to the rollout plan. Any risks/blockers/impediments? N/A   
    • Hide

      2026-04-22 - 🔵 Done
      Engineer(s): Dmitry Rybakov

      What was accomplished since the last update?

      • Implemented backpressure logic for retried and transactions, including the token bucket.

      What's the focus over the next two weeks?

      • Finalize the implementation according to the rollout plan.

      Any risks/blockers/impediments?

      • N/A 

       

      2026-04-13 - 🟢 On Track
      Engineer(s): Dmitry Rybakov

      What was accomplished since the last update?

      • Implemented backpressure logic for retried and transactions, including the token bucket.

      What's the focus over the next two weeks?

      • Finalize the implementation according to the rollout plan.

      Any risks/blockers/impediments?

      • N/A 

       

      2026-04-09 - 🟡 Potential Risk

      • Still working on withTransaction backoff and connection pool clearing changes
      • Not much progress during the last sprint, while the main implementer (Dmitry) was on an unplanned leave most of the sprint.
      • The confidence status changed to Potential Risk while Dmitry is now the sole spec owners of Transactions and Auth specs, as well as a co-owner of the OpenTelemetry spec. I am not sure whether this will actually add much of distractions, but it can. Hence the risk is "potential".

       

      2026-03-27 - 🟡 Potential Risk

      • Still working on withTransaction backoff and connection pool clearing changes
      • Not much progress during the last sprint, while the main implementer (Dmitry) was on an unplanned leave most of the sprint.
      • The confidence status changed to Potential Risk while Dmitry is now the sole spec owners of Transactions and Auth specs, as well as a co-owner of the OpenTelemetry spec. I am not sure whether this will actually add much of distractions, but it can. Hence the risk is "potential".

       

      Show
      2026-04-22 - 🔵 Done Engineer(s): Dmitry Rybakov What was accomplished since the last update? Implemented backpressure logic for retried and transactions, including the token bucket. What's the focus over the next two weeks? Finalize the implementation according to the rollout plan. Any risks/blockers/impediments? N/A    2026-04-13 - 🟢 On Track Engineer(s): Dmitry Rybakov What was accomplished since the last update? Implemented backpressure logic for retried and transactions, including the token bucket. What's the focus over the next two weeks? Finalize the implementation according to the rollout plan. Any risks/blockers/impediments? N/A    2026-04-09 - 🟡 Potential Risk Still working on withTransaction backoff and connection pool clearing changes Not much progress during the last sprint, while the main implementer (Dmitry) was on an unplanned leave most of the sprint. The confidence status changed to Potential Risk while Dmitry is now the sole spec owners of Transactions and Auth specs, as well as a co-owner of the OpenTelemetry spec. I am not sure whether this will actually add much of distractions, but it can. Hence the risk is "potential".   2026-03-27 - 🟡 Potential Risk Still working on withTransaction backoff and connection pool clearing changes Not much progress during the last sprint, while the main implementer (Dmitry) was on an unplanned leave most of the sprint. The confidence status changed to Potential Risk while Dmitry is now the sole spec owners of Transactions and Auth specs, as well as a co-owner of the OpenTelemetry spec. I am not sure whether this will actually add much of distractions, but it can. Hence the risk is "potential".  
    • Hide

      Summary of necessary driver changes

      •  

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      •  

      Context for other referenced/linked tickets

      •  
      Show
      Summary of necessary driver changes   Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed)   Context for other referenced/linked tickets  
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3160, please see that ticket for a detailed description.

            Assignee:
            Dmitry Rybakov
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              10 weeks, 3 days
              None
              None