[JAVA-692] Even when using db.requestStart/requestEnd, unpin member when read preference changes Created: 09/Nov/12  Updated: 31/Mar/15  Resolved: 12/Jul/13

Status: Closed
Project: Java Driver
Component/s: Connection Management
Affects Version/s: 2.9.3
Fix Version/s: 3.0.0

Type: Improvement Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-21 Unpin member when read preference cha... Closed
Related

 Description   

When the driver pins a thread to a socket using DB.requestStart(), it should remember the read preference used for the first read. If a subsequent read has a different read preference, unpin the member and start the member-selection process from scratch and rebind the thread to a different socket.

Currently, the driver ignores changes to read preference on queries performed within DB.requestStart/requestEnd boundaries.



 Comments   
Comment by Jeffrey Yemin [ 31/Mar/15 ]

Closing all resolved 3.0.0 issues, as 3.0.0 has been tagged and released.

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