top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the time limit for Mongos connecting to Mongod?

0 votes
412 views

I thought the time limit for Mongos to connect to Mongod was hard coded to 30 seconds. But some times after less than 2 seconds I see the following exception in the mongos logs -
Failed to connect to HOST:27017 - ExceededTimeLimit: Operation timed out
Any idea why?

posted Jun 20, 2018 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote
Lot of mongos processes are being created when sharded cluster is being initialized first time?

I am creating a sharded cluster with a 2 node config server replicaset.Due to some reason, the config server replicaset did not get created/setup properly.At this time, I started a mongos process configured to connect to this CSRS and on that box, I see lot of mongos processes getting created

Why wouldnt the mongos process just fail instead of keeping re-spawning and trying to connect to the CSRS? Related to this, how do we check (from an external script) that the CSRS is up & available before starting a mongos process?

The docs (https://docs.mongodb.com/manual/tutorial/troubleshoot-sharded-clusters/#sharding-config-servers-and-availability ) do mention that the CSRS should be available when you first initiate a sharded cluster, but does not mention how to do it.

0 votes
Starting mongod (via systemctl): Job for mongod.service failed because the control process exited with error code...

Starting mongod (via systemctl): Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.

Please guide me, how to overcome this issue.

0 votes
If you wanted to copy over the mongo database using mongos oplog, how would you do it?

If you wanted to copy over the mongo database using mongos oplog, how would you do it? Suppose we start copying the database at time T and we finish the copying at time U. We have to read from the oplog from time T onward and apply oplog changes (which also may have been applied between time T and U). Do the oplog transactions have timestamps in them so we can discard records before time T? Are the operations idempotent if we apply them twice (because we are applying an operation already executed between time T and U)? Guess I am confused how to get the initial data before reading from the oplog to continue the real time updates.

+2 votes
I followed the Ubuntu install instructions exactly, why is 3.0.5 using the 2.4 version config file i.e. mongod.conf

I followed the Ubuntu install instructions exactly, why is 3.0.5 using the 2.4 version config file, when all of MongoDB documentation uses the YAML format now for config options?

...