com.mongodb.MongoException: not talking to master and retries used up

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via JIRA by Vincent Sevel, 1 year ago
not talking to master and retries used up
via GitHub by jyemin
, 2 years ago
not talking to master and retries used up
via JIRA by Alvin Richards, 1 year ago
not talking to master and retries used up
via JIRA by Alvin Richards, 1 year ago
not talking to master and retries used up
via Google Groups by Chris Berry, 2 years ago
not talking to master and retries used up
via Pentaho BI Platform Tracking by Kaushal Sheth, 1 year ago
not talking to master and retries used up
com.mongodb.MongoException: not talking to master and retries used up
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:304)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:306)
at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:306)
at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:290)
at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:275)
at com.mongodb.DBCollection.findOne(DBCollection.java:727)
at com.mongodb.DBCollection.findOne(DBCollection.java:669)
at com.lodh.arte.test.robustmongo.ReproducerPrimaryPreferredSystemTest.readSecondary(ReproducerPrimaryPreferredSystemTest.java:87)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.