Client Backpressure

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.3.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Client Backpressure Spec
    • C Drivers
    • Completed
    • Done
    • 8
    • 11
    • 12
    • 50
    • 🔵 Done
    • Hide

      Engineer(s): Connor MacDonald
      2026-04-09: at risk for 2026-04-17

      • Possible path to Green: resolution of ongoing spec discussions (slack).
      • What was accomplished since the last update?
        • Merged fix to prose tests.
        • Reviewed changes to DRIVERS-3427.
      • What's the focus over the next two weeks?
        • Put C driver changes of DRIVERS-3427 in review once spec is decided.
      • Any risks/blockers/impediments?
        • Ongoing spec discussions.

       Updated "Final Cost Estimate" from 11 to 12 to agree with End Date.

      Show
      Engineer(s): Connor MacDonald 2026-04-09: at risk for 2026-04-17 Possible path to Green: resolution of ongoing spec discussions ( slack ). What was accomplished since the last update? Merged fix to prose tests. Reviewed changes to DRIVERS-3427 . What's the focus over the next two weeks? Put C driver changes of DRIVERS-3427 in review once spec is decided. Any risks/blockers/impediments? Ongoing spec discussions.  Updated "Final Cost Estimate" from 11 to 12 to agree with End Date.
    • Hide

      2026-04-17 - 🔵 Done
      Engineer(s): Connor MacDonald
      2026-04-09: at risk for 2026-04-17

      • Possible path to Green: resolution of ongoing spec discussions (slack).
      • What was accomplished since the last update?
        • Merged fix to prose tests.
        • Reviewed changes to DRIVERS-3427.
      • What's the focus over the next two weeks?
        • Put C driver changes of DRIVERS-3427 in review once spec is decided.
      • Any risks/blockers/impediments?
        • Ongoing spec discussions.

       Updated "Final Cost Estimate" from 11 to 12 to agree with End Date.

      2026-04-13 - 🟢 On Track
      Engineer(s): Connor MacDonald
      2026-04-09: at risk for 2026-04-17

      • Possible path to Green: resolution of ongoing spec discussions (slack).
      • What was accomplished since the last update?
        • Merged fix to prose tests.
        • Reviewed changes to DRIVERS-3427.
      • What's the focus over the next two weeks?
        • Put C driver changes of DRIVERS-3427 in review once spec is decided.
      • Any risks/blockers/impediments?
        • Ongoing spec discussions.

       Updated "Final Cost Estimate" from 11 to 12 to agree with End Date.

      2026-03-13 - 🟡 Potential Risk
      2026-03-13: Retry loop changes merged. Limiting deprioritization to replica sets merged. All current spec changes are implemented. End-date kept at March 20 (matches Project Overview). Marking as "Potential Risk" since I am not very confident in the new end-date as it depends on WRITING-36485 (see slack).

      2026-02-26 - 🟢 On Track
      Status update: Resumed project this week. End-date updated to March 20 (matches Project Overview).

      • Resuming work on retry loop changes.

      2026-01-20 - 🟢 On Track
      Status update:

      • In progress with Ezra (50%), Connor (100%), and Kevin (50%).
      • withTransaction retry changes merged
      • Deprioritization changes in progress
      • Connection pool clear changes in progress.

      Rationale for delays:

      • Testing discovered a bug in serverMonitoringMode (CDRIVER-6205).
      • Connection pool clearing complicated by existing tech debt.
      Show
      2026-04-17 - 🔵 Done Engineer(s): Connor MacDonald 2026-04-09: at risk for 2026-04-17 Possible path to Green: resolution of ongoing spec discussions ( slack ). What was accomplished since the last update? Merged fix to prose tests. Reviewed changes to DRIVERS-3427 . What's the focus over the next two weeks? Put C driver changes of DRIVERS-3427 in review once spec is decided. Any risks/blockers/impediments? Ongoing spec discussions.  Updated "Final Cost Estimate" from 11 to 12 to agree with End Date. 2026-04-13 - 🟢 On Track Engineer(s): Connor MacDonald 2026-04-09: at risk for 2026-04-17 Possible path to Green: resolution of ongoing spec discussions ( slack ). What was accomplished since the last update? Merged fix to prose tests. Reviewed changes to DRIVERS-3427 . What's the focus over the next two weeks? Put C driver changes of DRIVERS-3427 in review once spec is decided. Any risks/blockers/impediments? Ongoing spec discussions.  Updated "Final Cost Estimate" from 11 to 12 to agree with End Date. 2026-03-13 - 🟡 Potential Risk 2026-03-13: Retry loop changes merged. Limiting deprioritization to replica sets merged. All current spec changes are implemented. End-date kept at March 20 (matches Project Overview). Marking as "Potential Risk" since I am not very confident in the new end-date as it depends on WRITING-36485 (see slack). 2026-02-26 - 🟢 On Track Status update: Resumed project this week. End-date updated to March 20 (matches Project Overview ). Resuming work on retry loop changes. 2026-01-20 - 🟢 On Track Status update: In progress with Ezra (50%), Connor (100%), and Kevin (50%). withTransaction retry changes merged Deprioritization changes in progress Connection pool clear changes in progress. Rationale for delays: Testing discovered a bug in serverMonitoringMode ( CDRIVER-6205 ). Connection pool clearing complicated by existing tech debt.
    • 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:
            Connor MacDonald
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              13 weeks, 4 days
              None
              None