Client Backpressure with baseBackoffMS

XMLWordPrintableJSON

    • Needed
    • Hide

      Summary of necessary driver changes

      • Add support for baseBackoffMS to existing client backpressure drivers.
      • Update the manual backpressure support example code for your driver (DRIVERS-3584) in your codebase (if it exists) and in the document to support the new "baseBackoffMS" server error field
      • For the release notes associated with the backpressure v2 change, make sure to communicate:
        • "Improved performance for MongoDB 9.0's Intelligent Workload Management (IWM) by only retrying overload errors when doing so is expected to not worsen server conditions"
      • See d6fc118bd1dd6854fa72f9be0ff5d6a57e8f68e1

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

      Context for other referenced/linked tickets

      • See DRIVERS-3578 for a follow-up test fix.
      • Drivers are not required to link the IWM landing page information on their initial release notes. These should be retroactively added with DRIVERS-3606
      • Drivers are not required to reference or block on any IWM Atlas docs links in their in-driver code implementation. API references can be merged into the code base but do not need a prioritized release; they can accompany another release at the team's discretion
      Show
      Summary of necessary driver changes Add support for baseBackoffMS to existing client backpressure drivers. Update the manual backpressure support example code for your driver ( DRIVERS-3584 ) in your codebase (if it exists) and in the document to support the new "baseBackoffMS" server error field For the release notes associated with the backpressure v2 change, make sure to communicate: "Improved performance for MongoDB 9.0's Intelligent Workload Management (IWM) by only retrying overload errors when doing so is expected to not worsen server conditions" See d6fc118bd1dd6854fa72f9be0ff5d6a57e8f68e1 Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) d6fc118bd1dd6854fa72f9be0ff5d6a57e8f68e1 Context for other referenced/linked tickets See DRIVERS-3578 for a follow-up test fix. Drivers are not required to link the IWM landing page information on their initial release notes. These should be retroactively added with DRIVERS-3606 Drivers are not required to reference or block on any IWM Atlas docs links in their in-driver code implementation. API references can be merged into the code base but do not need a prioritized release; they can accompany another release at the team's discretion
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-6353 Done 2.5.0
      CXX-3518 Backlog
      CSHARP-6089 Done 3.11.0
      GODRIVER-3963 In Code Review
      JAVA-6238 Backlog
      NODE-7624 In Code Review
      PYTHON-5885 Fixed 4.18.0
      PHPLIB-1879 Blocked
      RUBY-3901 In Code Review
      RUST-2446 Fixed 3.9.0
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } #scriptField td.willNotDo { background-color: #FF0000; /* Red color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-6353 Done 2.5.0 CXX-3518 Backlog CSHARP-6089 Done 3.11.0 GODRIVER-3963 In Code Review JAVA-6238 Backlog NODE-7624 In Code Review PYTHON-5885 Fixed 4.18.0 PHPLIB-1879 Blocked RUBY-3901 In Code Review RUST-2446 Fixed 3.9.0

      Summary

      Implement baseBackoffMS when received as a signal from Client Backpressure.

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

      How likely is it that this problem or use case will occur?

      Main path? Edge case?

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      Is this ticket only for tests?

      Does this ticket have any functional impact, or is it just test improvements?

      Acceptance Criteria

      What specific requirements must be met to consider the design phase complete?

            Assignee:
            Noah Stapp
            Reporter:
            Jib Adegunloye
            Jib Adegunloye Jib Adegunloye
            Rishabh Bisht Rishabh Bisht
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: