[JAVA-1076] Deprecate autoConnectRetry and maxAutoConnectRetryTime Created: 13/Jan/14  Updated: 03/Apr/14  Resolved: 24/Jan/14

Status: Closed
Project: Java Driver
Component/s: Connection Management
Affects Version/s: None
Fix Version/s: 2.12.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

Issue Links:
Related
is related to JAVA-783 MongoClientURI doc is missing autocon... Closed
is related to JAVA-1096 Remove autoConnectRetry and maxAutoCo... Closed

 Description   

These options cause way too much confusion, and other drivers don't support them. People tend to think they are about retrying failed operations, when really they only pertain to retrying of socket connect. This is of marginal utility, since the maximum retry time allowed by most operating systems for socket connect is already fairly long.

Users should just set socketConnect to a large enough value for their application.



 Comments   
Comment by Githook User [ 04/Feb/14 ]

Author:

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

Message: JAVA-1076: Deprecate auto connect retry options in MongoOptions also
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/08f7e94b5937968f85802fbf0d81afaddef6fe3f

Comment by Githook User [ 15/Jan/14 ]

Author:

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

Message: JAVA-1076: Deprecate autoConnectRetry and maxAutoConnectRetryTime
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/754f82e00be45d6deb22eb99ecc14b913300dff1

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