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

Pentaho BI Platform Tracking | Kaushal Sheth | 4 years ago
  1. 0

    If I attempt to connect to a secondary (slave) Mongo instance and issue a query using the MongoDB Input step, I get the following error: INFO 17-07 13:17:28,459 - etl_test - Dispatching started for transformation [etl_test] ERROR 17-07 13:17:29,341 - MongoDb Input - Unexpected error ERROR 17-07 13:17:29,341 - MongoDb Input - com.mongodb.MongoException: not talking to master and retries used up at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:246) at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248) at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248) at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:305) at com.mongodb.DBCursor._check(DBCursor.java:369) at com.mongodb.DBCursor._hasNext(DBCursor.java:498) at com.mongodb.DBCursor.hasNext(DBCursor.java:523) at org.pentaho.di.trans.steps.mongodbinput.MongoDbInput.processRow(MongoDbInput.java:72) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50) at java.lang.Thread.run(Thread.java:662) I get similar errors if I use the mongo client to connect to the secondary and issue queries. The problem goes away in the client if I issue the command: rs.slaveOk() and then run my queries. Unfortunately, I see no way to execute this command when using the MongoDB Input step, so I am unable to query any data from the secondary MongoDB instance. In production environments, I would expect most queries to be run against secondaries rather than the master, especially for ETL, so I imagine this would be a blocker for many people. Hopefully it can be addressed soon.

    Pentaho BI Platform Tracking | 4 years ago | Kaushal Sheth
    com.mongodb.MongoException: not talking to master and retries used up
  2. 0

    If I attempt to connect to a secondary (slave) Mongo instance and issue a query using the MongoDB Input step, I get the following error: INFO 17-07 13:17:28,459 - etl_test - Dispatching started for transformation [etl_test] ERROR 17-07 13:17:29,341 - MongoDb Input - Unexpected error ERROR 17-07 13:17:29,341 - MongoDb Input - com.mongodb.MongoException: not talking to master and retries used up at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:246) at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248) at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248) at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:305) at com.mongodb.DBCursor._check(DBCursor.java:369) at com.mongodb.DBCursor._hasNext(DBCursor.java:498) at com.mongodb.DBCursor.hasNext(DBCursor.java:523) at org.pentaho.di.trans.steps.mongodbinput.MongoDbInput.processRow(MongoDbInput.java:72) at org.pentaho.di.trans.step.RunThread.run(RunThread.java:50) at java.lang.Thread.run(Thread.java:662) I get similar errors if I use the mongo client to connect to the secondary and issue queries. The problem goes away in the client if I issue the command: rs.slaveOk() and then run my queries. Unfortunately, I see no way to execute this command when using the MongoDB Input step, so I am unable to query any data from the secondary MongoDB instance. In production environments, I would expect most queries to be run against secondaries rather than the master, especially for ETL, so I imagine this would be a blocker for many people. Hopefully it can be addressed soon.

    Pentaho BI Platform Tracking | 4 years ago | Kaushal Sheth
    com.mongodb.MongoException: not talking to master and retries used up
  3. 0

    Response Not Received When There's a MongoException

    GitHub | 3 years ago | erturne
    com.mongodb.MongoException: not talking to master and retries used up
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GitHub comment 4#170865898

    GitHub | 11 months ago | mrfreezer
    com.mongodb.MongoException: not talking to master and retries used up
  6. 0

    [mongodb-user] Requests during initial Sync, java-Driver - Grokbase

    grokbase.com | 8 months ago
    com.mongodb.MongoException: not talking to master and retries used up

  1. sriharshakiran 2 times, last 7 months ago
5 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. com.mongodb.MongoException

    not talking to master and retries used up

    at com.mongodb.DBTCPConnector.call()
  2. MongoDB Java Driver
    DBCursor.hasNext
    1. com.mongodb.DBTCPConnector.call(DBTCPConnector.java:246)
    2. com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248)
    3. com.mongodb.DBTCPConnector.call(DBTCPConnector.java:248)
    4. com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:305)
    5. com.mongodb.DBCursor._check(DBCursor.java:369)
    6. com.mongodb.DBCursor._hasNext(DBCursor.java:498)
    7. com.mongodb.DBCursor.hasNext(DBCursor.java:523)
    7 frames
  3. org.pentaho.di
    RunThread.run
    1. org.pentaho.di.trans.steps.mongodbinput.MongoDbInput.processRow(MongoDbInput.java:72)
    2. org.pentaho.di.trans.step.RunThread.run(RunThread.java:50)
    2 frames
  4. Java RT
    Thread.run
    1. java.lang.Thread.run(Thread.java:662)
    1 frame