- start a new cluster with 3 config servers and one shard
- create a new sharded collection
- do some finds - all are fast (less than a second)
- block the first config server with iptables --DROP
- create a new connection
Looks like the python driver sends the "isMaster" command as the first op on the new connection, and it tries to do something funny:
2014-12-29T22:09:38.989+0000 I NETWORK [mongosMain] connection accepted from 192.168.0.1:53628 #3 (2 connections now open)
2014-12-29T22:09:38.990+0000 I NETWORK [conn3] SyncClusterConnection connecting to [mongo_CFG1:27017]
2014-12-29T22:09:43.990+0000 W NETWORK [conn3] Failed to connect to 192.168.0.97:27017 after 5000 milliseconds, giving up.
2014-12-29T22:09:43.990+0000 I NETWORK [conn3] SyncClusterConnection connect fail to: mongo_CFG1:27017 errmsg: couldn't connect to server mongo_CFG1:27017 (192.168.0.97), connection attempt failed
2014-12-29T22:09:43.990+0000 I NETWORK [conn3] SyncClusterConnection connecting to [mongo_CFG2:27017]
2014-12-29T22:09:43.991+0000 D NETWORK [conn3] connected to server mongo_CFG2:27017 (192.168.0.98)
2014-12-29T22:09:43.991+0000 I NETWORK [conn3] SyncClusterConnection connecting to [mongo_CFG3:27017]
2014-12-29T22:09:43.991+0000 D NETWORK [conn3] connected to server mongo_CFG3:27017 (192.168.0.99)
2014-12-29T22:09:43.991+0000 I NETWORK [conn3] unable to set SO_RCVTIMEO
2014-12-29T22:09:43.992+0000 I NETWORK [conn3] trying reconnect to mongo_CFG1:27017 (192.168.0.97) failed
2014-12-29T22:09:48.993+0000 W NETWORK [conn3] Failed to connect to 192.168.0.97:27017 after 5000 milliseconds, giving up.
2014-12-29T22:09:48.993+0000 I NETWORK [conn3] reconnect mongo_CFG1:27017 (192.168.0.97) failed failed couldn't connect to server mongo_CFG1:27017 (192.168.0.97), connection attempt failed
2014-12-29T22:09:48.993+0000 I NETWORK [conn3] query on config.databases: { _id: "admin" } failed to: mongo_CFG1:27017 (192.168.0.97) failed exception: socket exception [CONNECT_ERROR] for mongo_CFG1:27017 (192.168.0.97) failed
2014-12-29T22:09:48.993+0000 D SHARDING [conn3] DBConfig unserialize: admin { _id: "admin", partitioned: false, primary: "config" }
2014-12-29T22:09:48.995+0000 I NETWORK [conn3] trying reconnect to mongo_CFG1:27017 (192.168.0.97) failed
2014-12-29T22:09:53.995+0000 W NETWORK [conn3] Failed to connect to 192.168.0.97:27017 after 5000 milliseconds, giving up.
2014-12-29T22:09:53.995+0000 I NETWORK [conn3] reconnect mongo_CFG1:27017 (192.168.0.97) failed failed couldn't connect to server mongo_CFG1:27017 (192.168.0.97), connection attempt failed
2014-12-29T22:09:53.995+0000 I NETWORK [conn3] query on config.collections: { _id: /^admin\./ } failed to: mongo_CFG1:27017 (192.168.0.97) failed exception: socket exception [CONNECT_ERROR] for mongo_CFG1:27017 (192.168.0.97) failed
2014-12-29T22:09:53.996+0000 D SHARDING [conn3] found 0 dropped collections and 0 sharded collections for database admin
- is related to
-
SERVER-17617 One config server being down can block read operations on config data for seconds
-
- Closed
-