[SERVER-7746] Make replica set state transition smoother on the C++ driver Created: 22/Nov/12 Updated: 22/Nov/12 Resolved: 22/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client, Sharding |
| Affects Version/s: | 2.3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Whenever the configuration of a replica set changes, not all instances (whether they are kept by a thread servicing a client connection, idle in the pool or active) of the connections would know about this event. This can cause some unintuitive behaviors especially when mongos tries to use a very old replica set connection and gets a "not master" error. Proposed fix would be to make the replica set connection retry (meaning, re-evaluate the target host) when it gets the "not master" error (and perhaps consider for some class of errors as well) for the first time. |
| Comments |
| Comment by Randolph Tan [ 22/Nov/12 ] |
|
Please ignore - this is a misdiagnosis. |