Client Backpressure

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Affects Version/s: None
    • Component/s: None
    • Client Backpressure Spec
    • Go Drivers
    • Not Needed
    • Hide
      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
      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
    • 6
    • 7.5
    • 8
    • 33
    • 🟡 Potential Risk
    • Hide

      Engineer(s): Qingyang Hu, Sergey Zelenov

      What was accomplished since the last update?

      What's the focus over the next two weeks?

      Any risks/blockers/impediments?

      • No engineer will be able to review PRs from 3/20 to 4/3 because Sergey will be on vacation.
      Show
      Engineer(s): Qingyang Hu, Sergey Zelenov What was accomplished since the last update? DRIVERS-3378 ( GODRIVER-3778 ) Code examples for non-backpressure have been added to the Google doc. DRIVERS-3326 ( GODRIVER-3757 Handle `NoWritesPerformed` error label behavior for multiple retries) has been approved. We have decided to merge it with the exponential backoff ( DRIVERS-3239 / GODRIVER-3658 ) because it will have a better test coverage there. What's the focus over the next two weeks? DRIVERS-3391 ( GODRIVER-3810 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction) needs to address the review feedback. DRIVERS-3239 ( GODRIVER-3658 ) Implement exponential backoff/jitter in retry loops. Any risks/blockers/impediments? No engineer will be able to review PRs from 3/20 to 4/3 because Sergey will be on vacation.
    • Hide

      2026-03-27 - 🟡 Potential Risk
      Engineer(s): Qingyang Hu, Sergey Zelenov

      What was accomplished since the last update?

      What's the focus over the next two weeks?

      Any risks/blockers/impediments?

      • No engineer will be able to review PRs from 3/20 to 4/3 because Sergey will be on vacation.

      2026-03-13 - 🟢 On Track
      Engineer(s): Qingyang Hu, Sergey Zelenov

      What was accomplished since the last update?

      • DRIVERS-3218 (GODRIVER-3646 Avoid connection pool clearing in rate limit circumstances) has been merged into the code base.
      • DRIVERS-3326 (GODRIVER-3757 Handle `NoWritesPerformed` error label behavior for multiple retries) has been implemented and is under active review.
      • DRIVERS-3378 (GODRIVER-3778 Code examples for non-backpressure drivers handling backpressure errors) is under active review.

      What's the focus over the next two weeks?

      • Catch up on the code review.
      • DRIVERS-3239 (GODRIVER-3658) Implement exponential backoff/jitter in retry loops and token bucket support.

      Any risks/blockers/impediments?

      • None

      2026-02-27 - 🟡 Potential Risk
      GODRIVER-3647 is done. GODRIVER-3646 is under review.
      Slow in reviewing the PRs due to understaffing.

      2026-02-13 - No confidence status provided
      GODRIVER-3646 and GODRIVER-3647 are in progress.

      Show
      2026-03-27 - 🟡 Potential Risk Engineer(s): Qingyang Hu, Sergey Zelenov What was accomplished since the last update? DRIVERS-3378 ( GODRIVER-3778 ) Code examples for non-backpressure have been added to the Google doc. DRIVERS-3326 ( GODRIVER-3757 Handle `NoWritesPerformed` error label behavior for multiple retries) has been approved. We have decided to merge it with the exponential backoff ( DRIVERS-3239 / GODRIVER-3658 ) because it will have a better test coverage there. What's the focus over the next two weeks? DRIVERS-3391 ( GODRIVER-3810 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction) needs to address the review feedback. DRIVERS-3239 ( GODRIVER-3658 ) Implement exponential backoff/jitter in retry loops. Any risks/blockers/impediments? No engineer will be able to review PRs from 3/20 to 4/3 because Sergey will be on vacation. 2026-03-13 - 🟢 On Track Engineer(s): Qingyang Hu, Sergey Zelenov What was accomplished since the last update? DRIVERS-3218 ( GODRIVER-3646 Avoid connection pool clearing in rate limit circumstances) has been merged into the code base. DRIVERS-3326 ( GODRIVER-3757 Handle `NoWritesPerformed` error label behavior for multiple retries) has been implemented and is under active review. DRIVERS-3378 ( GODRIVER-3778 Code examples for non-backpressure drivers handling backpressure errors) is under active review. What's the focus over the next two weeks? Catch up on the code review. DRIVERS-3239 ( GODRIVER-3658 ) Implement exponential backoff/jitter in retry loops and token bucket support. Any risks/blockers/impediments? None 2026-02-27 - 🟡 Potential Risk GODRIVER-3647 is done. GODRIVER-3646 is under review. Slow in reviewing the PRs due to understaffing. 2026-02-13 - No confidence status provided GODRIVER-3646 and GODRIVER-3647 are in progress.
    • 8
    • 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:
            Qingyang Hu
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              11 weeks, 3 days
              None
              None