Client Backpressure for IWM 9.0 Release

XMLWordPrintableJSON

    • IWM Client Backpressure for 9.0 Release
    • Python Drivers
    • None
    • 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  
    • In Progress
    • 16
    • 8
    • 0
    • 100
    • -50
    • 🟢 On Track
    • Hide
      • (WRITING-38670) Constructed timeline estimation for internal DBX leads to agree on a code completion date
      • (SERVER-130142) Initial specification still under review. Also awaiting (SERVER-130142) to renamed retryAfterMS to baseBackoffMS
      • (DRIVERS-3530) Decision made on update to release notes. Awaiting changes from all teams.
      • Given no further plans to implement newer workloads, DRIVER’s commitment is to pass the pinned version; this is trivial and has been done against the PoC
      Show
      (WRITING-38670) Constructed timeline estimation for internal DBX leads to agree on a code completion date ( SERVER-130142 ) Initial specification still under review. Also awaiting ( SERVER-130142 ) to renamed retryAfterMS to baseBackoffMS (DRIVERS-3530) Decision made on update to release notes. Awaiting changes from all teams. Given no further plans to implement newer workloads, DRIVER’s commitment is to pass the pinned version; this is trivial and has been done against the PoC
    • Hide

      2026-07-07 - 🟢 On Track

      • (WRITING-38670) Constructed timeline estimation for internal DBX leads to agree on a code completion date
      • (SERVER-130142) Initial specification still under review. Also awaiting (SERVER-130142) to renamed retryAfterMS to baseBackoffMS
      • (DRIVERS-3530) Decision made on update to release notes. Awaiting changes from all teams.
      • Given no further plans to implement newer workloads, DRIVER’s commitment is to pass the pinned version; this is trivial and has been done against the PoC

      2026-06-24 - 🟢 On Track

      • Retryability timeline document approved. Describes work estimates and slated set of work will be tackled in order to achieve 9.0
      • (WRITING-37844) IWM 9.0 retryAfterMS sketch made and approved. Detailed the PoC to confirm data on simulations and ensure retryAfterMS doesn't lead to unexpected regressions.
      • https://jira.mongodb.org/browse/PERF-8759 perf testing followed
      • Results ultimately inconclusive on improved behavior in availability. Did not make it worse.
      • (WRITING-37915) Agreed in metric and motivation doc to only have error rate, latency, and throughput as guardrail metrics but move forward with retryAfterMS due to infrastructural benefits provided by the server configurability
      • (DRIVERS-3535) initial specification created and under review.
      • Selected C# as second implementer
      • Updated release note guidance on DRIVERS-3530 to state all drivers should remove hyperlinks in their release notes and state IWM apis will support 9.0
      Show
      2026-07-07 - 🟢 On Track (WRITING-38670) Constructed timeline estimation for internal DBX leads to agree on a code completion date ( SERVER-130142 ) Initial specification still under review. Also awaiting ( SERVER-130142 ) to renamed retryAfterMS to baseBackoffMS (DRIVERS-3530) Decision made on update to release notes. Awaiting changes from all teams. Given no further plans to implement newer workloads, DRIVER’s commitment is to pass the pinned version; this is trivial and has been done against the PoC 2026-06-24 - 🟢 On Track Retryability timeline document approved. Describes work estimates and slated set of work will be tackled in order to achieve 9.0 (WRITING-37844) IWM 9.0 retryAfterMS sketch made and approved. Detailed the PoC to confirm data on simulations and ensure retryAfterMS doesn't lead to unexpected regressions. https://jira.mongodb.org/browse/PERF-8759 perf testing followed Results ultimately inconclusive on improved behavior in availability. Did not make it worse. (WRITING-37915) Agreed in metric and motivation doc to only have error rate, latency, and throughput as guardrail metrics but move forward with retryAfterMS due to infrastructural benefits provided by the server configurability ( DRIVERS-3535 ) initial specification created and under review. Selected C# as second implementer Updated release note guidance on DRIVERS-3530 to state all drivers should remove hyperlinks in their release notes and state IWM apis will support 9.0
    • Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      The server will start to shed load during overload Targeting 9.0. We need a spec to do so safely and correctly.

      Motivation

      This is a critical piece of improving MongoDB Availability.

            Assignee:
            Jib Adegunloye
            Reporter:
            Jib Adegunloye
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              16 weeks
              None