-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Backpressure
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a... user of the V6 driver
I want... the client backpressure changes to be in v6
So that... I can get the improved availability experience without upgrading a major driver version
User Experience
- V6 users connecting to new server clusters with load shedding enabled have client backpressure applied.
Dependencies
- NODE-7105 has to be completed first
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- Backport all backpressure changes made in NODE-7105 to V6
Testing Requirements
- Backport all relevant testing done in NODE-7105 to V6
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- depends on
-
NODE-7106 node-mongodb-native - PR #4618: fix(deps): tar-fs can extract outside the specified dir with a specific tarball
-
- Closed
-