[JAVA-271] Java client does not gracefully handle a replication set failure Created: 13/Feb/11 Updated: 25/Jun/13 Resolved: 24/Oct/11 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Cluster Management |
| Affects Version/s: | 2.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tony Nelson | Assignee: | Antoine Girbal |
| Resolution: | Cannot Reproduce | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu Server 10.04 LTS, Mongo 1.6.5 from 10gen repository |
||
| Description |
|
Simply put, when a client is connected to a replica set and the replica set fails over from one master to another, the Mongo instance never detects the change and continues to erroneously send all commands to the old slave. This was discussed on the mailing list here: http://groups.google.com/group/mongodb-user/browse_thread/thread/798f269f0882a16c Per Scott Hernandez's suggestion I have created an example of the failure that runs like as a maven test case git://github.com/hhubris/mongo-fail-demo.git Creating a new Mongo object works around the problem, but it doesn't feel like the right solution. Thanks again for all the help. |
| Comments |
| Comment by Tony Nelson [ 24/Oct/11 ] |
|
This seems to be fixed in the 2.6.5 driver, if not before. Thank you very much. |
| Comment by Scott Hernandez (Inactive) [ 24/Oct/11 ] |
|
This should be fixed in newer versions of the driver, can you please try them? |