[JAVA-1499] When pinning connection for reads, use same server as writes when reading from a primary Created: 10/Oct/14  Updated: 31/Mar/15  Resolved: 11/Oct/14

Status: Closed
Project: Java Driver
Component/s: Session Management
Affects Version/s: None
Fix Version/s: 3.0.0

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


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

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

Comment by Githook User [ 30/Jan/15 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: When pinning connection for reads, use same server as writes when reading from a primary

JAVA-1499
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/3a5258373326e938aa78caaf53502744b4a3efca

Comment by Githook User [ 11/Oct/14 ]

Author:

{u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}

Message: When pinning connection for reads, use same server as writes when reading from a primary

JAVA-1499
Branch: 3.0.x
https://github.com/mongodb/mongo-java-driver/commit/3a5258373326e938aa78caaf53502744b4a3efca

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