-
Type: Task
-
Resolution: Won't Fix
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.6.5
-
Component/s: Performance
-
Labels:None
We are using Java Driver 2.6.5. Our biggest issues with the driver are the # of connections it uses (no shrinking, synchronous connection model), and lack of connection health management (when there are mongod segfault/failovers we will see exceptions hours later because bad connections aren't cleaned up).
I haven't seen much progress on this front in the last 6 months or so and I still see tickets like, https://jira.mongodb.org/browse/JAVA-424, unprioritized.
I would appreciate some comments on this and what the current plan is for the Java driver.