[DRIVERS-1847] Improve guidance around connection pinning on error in cursors Created: 13/Jul/21  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: Load Balancer
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Matt Broadstone Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Driver Changes: Needed

 Description   

The load balancer spec currently states:

If a getMore fails with a network error, drivers MUST leave the connection pinned to the cursor.

however, we have tests which prove that we also do not unpin on non-network errors. I think the spec language should be changed to state that we should not unpin on any error.

Additionally, drivers which have lazy cursors (like the Node driver) may need to distinguish pinning rules between cursor initialization and iteration. I suggest an update to state that all errors on initialization should not pin, while errors on getMore should follow the rules above.



 Comments   
Comment by Alexander Golin (Inactive) [ 26/Jul/21 ]

Based on the triage discussion amongst the leads, we are opting to put this in the backlog for now. If any driver teams are experiencing a lot of pain around this issue, please capture it here and we will reprioritize.

Generated at Thu Feb 08 08:24:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.