[SERVER-7274] Check on connect() for DBClientRS? Created: 05/Oct/12  Updated: 10/Dec/14  Resolved: 30/Jan/14

Status: Closed
Project: Core Server
Component/s: Internal Client, Networking
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Mathias Stearn
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12284 ReplicaSetMonitor is broken Closed
Operating System: ALL
Participants:

 Description   

With the change to isAnyNodeOk() in DBClientRS::connect(), we rely on the ReplicaSetMonitorWatcher to keep us up-to-date (if it's stale, our connections will fail). This behavior is different from previous, where we actively checked the replica set again for activity.

Think if we aren't able to find nodes we know are ok, we should re-check the nodes. A timed backoff may be appropriate as well to avoid spamming reconnect requests.



 Comments   
Comment by Daniel Pasette (Inactive) [ 30/Jan/14 ]

this was fixed with SERVER-12284

Comment by Mathias Stearn [ 24/Jan/14 ]

The current version of the SERVER-12284 rewrite maintains existing behavior of returning cached data. It would be a one-line change to change that though.

Comment by auto [ 05/Oct/12 ]

Author:

{u'date': u'2012-10-05T08:54:29-07:00', u'email': u'greg@10gen.com', u'name': u'Greg Studer'}

Message: buildbot stale_clustered.js also need to check whether mongos knows about new conns, pending SERVER-7274
Branch: master
https://github.com/mongodb/mongo/commit/12c9729212df16946bcc152b459bd9253d16bde3

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