[JAVA-350] com.mongodb.MongoException: not talking to master and retries used up Created: 12/May/11 Updated: 09/Jan/14 Resolved: 10/Aug/12 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Conigliaro | Assignee: | Brendan W. McAdams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
After replica set failover in my sharded cluster, my app throws exceptions like this: ERR [20110512-15:47:43.401] blueeyes: com.mongodb.MongoException: not talking to master and retries used up This may be related to https://jira.mongodb.org/browse/SERVER-3087 |
| Comments |
| Comment by Marius Seritan [ 13/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I apologize this was a mistake on our side. A combination of configuration changes and using mongo driver in single mode lead to us sending write requests to the slave in one of the components. Sorry for the noise. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Marius Seritan [ 13/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Problem is still occuring after updating all the servers in the replica set to 2.0.6. It turns out we are using mongo-java-driver-2.6.5.jar, will try to update to the latest. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Marius Seritan [ 13/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am getting these errors with just sone of the importers running. See the rs.status() below. The master we want to use is us-east1b and I ran the status command on that master. I am not sure if syncingTo is correct. One more detail that may be criticak to mention: us-east1b and us-east3 run mongodb 2.0.5, us-west1 runs mongodb 2.0.6 since yesterday. Can this be the cause of these problems? I will upgrade now the other servers.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Marius Seritan [ 13/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am also getting this error today. I am not aware of any change in the replica set master. I do not see errors in the logs. Some more data points, may or may not be relevant:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 12/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We should print the replset status with the exception for better debuging | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Jeffrey Yemin [ 12/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@Nic, is this a three node replica set? If so, and two of the nodes were down, there wouldn't have been a master, and the driver would not be able to write or read (unless using slaveOk). | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Nic Cottrell (Personal) [ 12/Jun/12 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I just got this with server 2.0.5 and java client drivers 2.7.3. The server was part of a replica set, but the arbiter and other node have been down for weeks and this was the first time I saw this message. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 08/Dec/11 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Are you sure there is a mater currently? | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Amit [ 08/Dec/11 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Any workaround / patch for this issue ? Facing the same issue with a replica set of 2 DB + 1 arbiter | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Nic Cottrell (Personal) [ 05/Nov/11 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I just got this too: com.mongodb.MongoException: not talking to master and retries used up But I am running a single instance server with journalling... not replicas at all. |