2016-03-09T00:57:06.721-0500 I CONTROL [main] ***** SERVER RESTARTED ***** 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] MongoDB starting : pid=32168 port=27017 dbpath=/home/sysadmin/mongodb/db 64-bit host=dbtest05 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] db version v3.2.3 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] git version: b326ba837cf6f49d65c2f85e1b70f6f31ece7937 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] allocator: tcmalloc 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] modules: none 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] build environment: 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] distmod: ubuntu1404 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] distarch: x86_64 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] target_arch: x86_64 2016-03-09T00:57:06.787-0500 I CONTROL [initandlisten] options: { config: "/home/sysadmin/mongodb/mongod.conf", net: { bindIp: "192.168.200.5", maxIncomingConnections: 65535, port: 27017, unixDomainSocket: { enabled: true, filePermissions: 448, pathPrefix: "/home/sysadmin/mongodb/socket" } }, processManagement: { fork: true, pidFilePath: "/home/sysadmin/mongodb/pid" }, replication: { oplogSizeMB: 4096, replSetName: "rs0", secondaryIndexPrefetch: "all" }, storage: { dbPath: "/home/sysadmin/mongodb/db", engine: "mmapv1", journal: { enabled: false }, mmapv1: { smallFiles: true } }, systemLog: { component: { replication: { verbosity: 5 } }, destination: "file", logAppend: true, logRotate: "reopen", path: "/home/sysadmin/mongodb/log/mongod.log", traceAllExceptions: false, verbosity: 0 } } 2016-03-09T00:57:06.787-0500 I NETWORK [initandlisten] --maxConns too high, can only handle 819 2016-03-09T00:57:06.814-0500 I INDEX [initandlisten] allocating new ns file /home/sysadmin/mongodb/db/local.ns, filling with zeroes... 2016-03-09T00:57:06.855-0500 I STORAGE [FileAllocator] allocating new datafile /home/sysadmin/mongodb/db/local.0, filling with zeroes... 2016-03-09T00:57:06.855-0500 I STORAGE [FileAllocator] creating directory /home/sysadmin/mongodb/db/_tmp 2016-03-09T00:57:06.856-0500 I STORAGE [FileAllocator] done allocating datafile /home/sysadmin/mongodb/db/local.0, size: 16MB, took 0 secs 2016-03-09T00:57:06.860-0500 I REPL [initandlisten] Did not find local voted for document at startup; NoMatchingDocument: Did not find replica set lastVote document in local.replset.election 2016-03-09T00:57:06.861-0500 I REPL [initandlisten] Did not find local replica set configuration document at startup; NoMatchingDocument: Did not find replica set configuration document in local.system.replset 2016-03-09T00:57:06.861-0500 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/home/sysadmin/mongodb/db/diagnostic.data' 2016-03-09T00:57:06.861-0500 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker 2016-03-09T00:57:06.862-0500 I NETWORK [initandlisten] waiting for connections on port 27017 2016-03-09T00:57:25.973-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.1:58957 #1 (1 connection now open) 2016-03-09T00:57:25.974-0500 I NETWORK [conn1] end connection 192.168.200.1:58957 (0 connections now open) 2016-03-09T00:57:25.975-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.1:58958 #2 (1 connection now open) 2016-03-09T00:57:25.978-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:25.978Z 2016-03-09T00:57:25.981-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.1:27017 2016-03-09T00:57:25.984-0500 D REPL [ReplicationExecutor] Cannot update term in election protocol version 0 2016-03-09T00:57:25.984-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:27.984Z 2016-03-09T00:57:25.984-0500 D REPL [ReplicationExecutor] Received new config via heartbeat with version 5 2016-03-09T00:57:25.987-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.2:57155 #3 (2 connections now open) 2016-03-09T00:57:25.987-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.4:47945 #4 (3 connections now open) 2016-03-09T00:57:25.988-0500 I NETWORK [conn3] end connection 192.168.200.2:57155 (2 connections now open) 2016-03-09T00:57:25.988-0500 I NETWORK [conn4] end connection 192.168.200.4:47945 (1 connection now open) 2016-03-09T00:57:25.989-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.3:55306 #5 (2 connections now open) 2016-03-09T00:57:25.990-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.2:57156 #6 (3 connections now open) 2016-03-09T00:57:25.990-0500 I NETWORK [conn5] end connection 192.168.200.3:55306 (1 connection now open) 2016-03-09T00:57:25.991-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.4:47946 #7 (3 connections now open) 2016-03-09T00:57:25.992-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:25.992Z 2016-03-09T00:57:25.992-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:25.992Z 2016-03-09T00:57:25.993-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.3:55309 #8 (4 connections now open) 2016-03-09T00:57:25.994-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.2:27017 2016-03-09T00:57:25.996-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.4:27017 2016-03-09T00:57:25.996-0500 D REPL [ReplicationExecutor] Cannot update term in election protocol version 0 2016-03-09T00:57:25.996-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:27.996Z 2016-03-09T00:57:25.997-0500 D REPL [ReplicationExecutor] Ignoring new configuration with version 5 because already in the midst of a configuration process 2016-03-09T00:57:25.997-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:25.997Z 2016-03-09T00:57:25.997-0500 D REPL [ReplicationExecutor] Cannot update term in election protocol version 0 2016-03-09T00:57:25.997-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:27.997Z 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Ignoring new configuration with version 5 because already in the midst of a configuration process 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Updated term in topology coordinator to 0 due to new config 2016-03-09T00:57:25.998-0500 I REPL [ReplicationExecutor] New replica set config in use: { _id: "rs0", version: 5, protocolVersion: 1, members: [ { _id: 0, host: "192.168.200.1:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "192.168.200.2:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "192.168.200.3:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 3, host: "192.168.200.4:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 4, host: "192.168.200.5:27017", arbiterOnly: true, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 } } } 2016-03-09T00:57:25.998-0500 I REPL [ReplicationExecutor] This node is 192.168.200.5:27017 in the config 2016-03-09T00:57:25.998-0500 I REPL [ReplicationExecutor] transition to ARBITER 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:25.998Z 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:25.998Z 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:25.998Z 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:25.998Z 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:25.998-0500 2016-03-09T00:57:25.998-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:25.998-0500 2016-03-09T00:57:25.999-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:25.998-0500 2016-03-09T00:57:25.999-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:25.998-0500 2016-03-09T00:57:25.999-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T00:57:25.998-0500 2016-03-09T00:57:25.999-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:57:35.998-0500 2016-03-09T00:57:25.999-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.3:27017 2016-03-09T00:57:26.000-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:26.000-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state STARTUP2 2016-03-09T00:57:26.000-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:31.000Z 2016-03-09T00:57:26.000-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:26.001-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state STARTUP2 2016-03-09T00:57:26.001-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:31.000Z 2016-03-09T00:57:26.001-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:26.001-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state PRIMARY 2016-03-09T00:57:26.001-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:31.001Z 2016-03-09T00:57:26.001-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:26.001-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state STARTUP2 2016-03-09T00:57:26.001-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:31.001Z 2016-03-09T00:57:26.001-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.3:27017 2016-03-09T00:57:26.140-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.1:58962 #9 (5 connections now open) 2016-03-09T00:57:26.141-0500 I NETWORK [conn9] end connection 192.168.200.1:58962 (4 connections now open) 2016-03-09T00:57:26.142-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:26.142Z 2016-03-09T00:57:26.144-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:26.144-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:31.144Z 2016-03-09T00:57:26.145-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:26.145Z 2016-03-09T00:57:26.147-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:31.147Z 2016-03-09T00:57:26.147-0500 D REPL [ReplicationExecutor] Received new config via heartbeat with version 6 2016-03-09T00:57:26.154-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.2:57161 #10 (5 connections now open) 2016-03-09T00:57:26.154-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.4:47950 #11 (6 connections now open) 2016-03-09T00:57:26.155-0500 I NETWORK [conn10] end connection 192.168.200.2:57161 (5 connections now open) 2016-03-09T00:57:26.155-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.3:55313 #12 (6 connections now open) 2016-03-09T00:57:26.156-0500 I NETWORK [conn11] end connection 192.168.200.4:47950 (5 connections now open) 2016-03-09T00:57:26.157-0500 I NETWORK [conn12] end connection 192.168.200.3:55313 (4 connections now open) 2016-03-09T00:57:26.158-0500 I REPL [ReplicationExecutor] New replica set config in use: { _id: "rs0", version: 6, protocolVersion: 1, members: [ { _id: 0, host: "192.168.200.1:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { dc_one: "node1" }, slaveDelay: 0, votes: 1 }, { _id: 1, host: "192.168.200.2:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { dc_one: "node2" }, slaveDelay: 0, votes: 1 }, { _id: 2, host: "192.168.200.3:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { dc_two: "node1" }, slaveDelay: 0, votes: 1 }, { _id: 3, host: "192.168.200.4:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: { dc_two: "node2" }, slaveDelay: 0, votes: 1 }, { _id: 4, host: "192.168.200.5:27017", arbiterOnly: true, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, getLastErrorModes: { WC2: { dc_one: 2 }, WC3: { dc_one: 2, dc_two: 1 } }, getLastErrorDefaults: { w: 1, wtimeout: 0 } } } 2016-03-09T00:57:26.158-0500 I REPL [ReplicationExecutor] This node is 192.168.200.5:27017 in the config 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:26.158Z 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:26.158Z 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:26.158Z 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:26.158Z 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:26.158-0500 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:26.158-0500 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:26.158-0500 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:26.158-0500 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T00:57:26.158-0500 2016-03-09T00:57:26.158-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:57:36.158-0500 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:31.160Z 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:31.160Z 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:31.160Z 2016-03-09T00:57:26.160-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:26.161-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:31.160Z 2016-03-09T00:57:31.163-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:31.163-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state SECONDARY 2016-03-09T00:57:31.163-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:36.163Z 2016-03-09T00:57:31.163-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:31.163-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state SECONDARY 2016-03-09T00:57:31.164-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:36.163Z 2016-03-09T00:57:31.164-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:31.164-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state SECONDARY 2016-03-09T00:57:31.164-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:36.164Z 2016-03-09T00:57:31.164-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:31.164-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:36.164Z 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:36.157-0500 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:32.563-0500 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:32.709-0500 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:32.853-0500 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:57:32.563-0500 2016-03-09T00:57:36.158-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:57:42.563-0500 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:41.165Z 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:41.166Z 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:41.166Z 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:36.166-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:41.166Z 2016-03-09T00:57:41.168-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:41.168-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:46.168Z 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:46.169Z 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:46.169Z 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:41.169-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:46.169Z 2016-03-09T00:57:42.563-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:42.164-0500 2016-03-09T00:57:42.563-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:41.571-0500 2016-03-09T00:57:42.564-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:41.717-0500 2016-03-09T00:57:42.564-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:41.860-0500 2016-03-09T00:57:42.564-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:57:41.571-0500 2016-03-09T00:57:42.564-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:57:51.571-0500 2016-03-09T00:57:46.170-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:51.170Z 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:51.171Z 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:51.171Z 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:46.171-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:51.171Z 2016-03-09T00:57:51.173-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:51.173-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:57:56.173Z 2016-03-09T00:57:51.174-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:51.174-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:57:56.174Z 2016-03-09T00:57:51.174-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:51.174-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:57:56.174Z 2016-03-09T00:57:51.175-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:51.175-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:57:56.175Z 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:50.173-0500 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:49.584-0500 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:49.726-0500 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:49.869-0500 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:57:49.584-0500 2016-03-09T00:57:51.571-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:57:59.584-0500 2016-03-09T00:57:56.176-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:57:56.176-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:01.176Z 2016-03-09T00:57:56.176-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:57:56.176-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:01.176Z 2016-03-09T00:57:56.177-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:57:56.177-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:01.177Z 2016-03-09T00:57:56.177-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:57:56.177-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:01.177Z 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:58.183-0500 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:57.597-0500 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:57.736-0500 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:57:57.879-0500 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:57:57.597-0500 2016-03-09T00:57:59.584-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:07.597-0500 2016-03-09T00:58:01.178-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:01.178-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:06.178Z 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:06.179Z 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:06.179Z 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:01.179-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:06.179Z 2016-03-09T00:58:06.180-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:06.180-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:11.180Z 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:11.181Z 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:11.181Z 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:06.181-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:11.181Z 2016-03-09T00:58:07.597-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:06.192-0500 2016-03-09T00:58:07.597-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:05.607-0500 2016-03-09T00:58:07.597-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:05.748-0500 2016-03-09T00:58:07.597-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:05.889-0500 2016-03-09T00:58:07.597-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:05.607-0500 2016-03-09T00:58:07.598-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:15.607-0500 2016-03-09T00:58:11.183-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:11.183-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:16.183Z 2016-03-09T00:58:11.183-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:11.183-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:16.183Z 2016-03-09T00:58:11.184-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:11.184-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:16.184Z 2016-03-09T00:58:11.184-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:11.184-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:16.184Z 2016-03-09T00:58:15.607-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:14.203-0500 2016-03-09T00:58:15.608-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:13.619-0500 2016-03-09T00:58:15.608-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:13.758-0500 2016-03-09T00:58:15.608-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:13.901-0500 2016-03-09T00:58:15.608-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:13.619-0500 2016-03-09T00:58:15.608-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:23.619-0500 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:21.186Z 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:21.186Z 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:16.186-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:21.186Z 2016-03-09T00:58:16.187-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:16.187-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:21.187Z 2016-03-09T00:58:17.308-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.5:34129 #13 (5 connections now open) 2016-03-09T00:58:21.189-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:21.189-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:26.189Z 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:26.190Z 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:26.190Z 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:21.190-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:26.190Z 2016-03-09T00:58:23.619-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:22.212-0500 2016-03-09T00:58:23.619-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:21.633-0500 2016-03-09T00:58:23.620-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:21.768-0500 2016-03-09T00:58:23.620-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:21.910-0500 2016-03-09T00:58:23.620-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:21.633-0500 2016-03-09T00:58:23.620-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:31.633-0500 2016-03-09T00:58:26.192-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:26.192-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:31.192Z 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:31.193Z 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:31.193Z 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:26.193-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:31.193Z 2016-03-09T00:58:31.195-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:31.195-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:36.195Z 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:36.196Z 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:36.196Z 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:31.196-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:36.196Z 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:30.221-0500 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:29.646-0500 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:29.779-0500 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:29.920-0500 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:29.646-0500 2016-03-09T00:58:31.633-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:39.646-0500 2016-03-09T00:58:36.198-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:36.198-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:41.198Z 2016-03-09T00:58:36.198-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:36.199-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:41.198Z 2016-03-09T00:58:36.199-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:36.199-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:41.199Z 2016-03-09T00:58:36.199-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:36.199-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:41.199Z 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:38.232-0500 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:37.657-0500 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:37.792-0500 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:37.930-0500 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:37.657-0500 2016-03-09T00:58:39.646-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:47.657-0500 2016-03-09T00:58:41.201-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:41.201-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:46.201Z 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:46.202Z 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:46.202Z 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:41.202-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:46.202Z 2016-03-09T00:58:46.203-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:46.203-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:51.203Z 2016-03-09T00:58:46.204-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:46.204-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:51.204Z 2016-03-09T00:58:46.204-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:46.204-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:51.204Z 2016-03-09T00:58:46.204-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:46.205-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:51.204Z 2016-03-09T00:58:47.657-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:46.240-0500 2016-03-09T00:58:47.658-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:45.670-0500 2016-03-09T00:58:47.658-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:45.802-0500 2016-03-09T00:58:47.658-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:45.940-0500 2016-03-09T00:58:47.658-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:45.670-0500 2016-03-09T00:58:47.658-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:58:55.670-0500 2016-03-09T00:58:51.206-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:51.206-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:58:56.206Z 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:58:56.207Z 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:58:56.207Z 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:51.207-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:58:56.207Z 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:54.250-0500 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:53.682-0500 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:53.812-0500 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:58:53.949-0500 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:58:53.682-0500 2016-03-09T00:58:55.671-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:03.682-0500 2016-03-09T00:58:56.208-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:58:56.209-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:01.208Z 2016-03-09T00:58:56.209-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:58:56.209-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:01.209Z 2016-03-09T00:58:56.209-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:58:56.210-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:01.209Z 2016-03-09T00:58:56.210-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:58:56.210-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:01.210Z 2016-03-09T00:59:01.211-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:01.212-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:06.211Z 2016-03-09T00:59:01.212-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:01.212-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:06.212Z 2016-03-09T00:59:01.212-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:01.212-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:06.212Z 2016-03-09T00:59:01.213-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:01.213-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:06.213Z 2016-03-09T00:59:03.682-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:02.262-0500 2016-03-09T00:59:03.683-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:01.694-0500 2016-03-09T00:59:03.683-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:01.823-0500 2016-03-09T00:59:03.683-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:01.960-0500 2016-03-09T00:59:03.683-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:01.694-0500 2016-03-09T00:59:03.683-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:11.694-0500 2016-03-09T00:59:06.214-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:06.214-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:11.214Z 2016-03-09T00:59:06.214-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:06.214-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:11.214Z 2016-03-09T00:59:06.215-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:06.215-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:11.215Z 2016-03-09T00:59:06.215-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:06.215-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:11.215Z 2016-03-09T00:59:11.216-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:11.216-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:16.216Z 2016-03-09T00:59:11.217-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:11.217-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:16.217Z 2016-03-09T00:59:11.217-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:11.217-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:16.217Z 2016-03-09T00:59:11.218-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:11.218-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:16.218Z 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:10.273-0500 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:09.705-0500 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:09.833-0500 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:09.967-0500 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:09.705-0500 2016-03-09T00:59:11.694-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:19.705-0500 2016-03-09T00:59:16.219-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:16.219-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:21.219Z 2016-03-09T00:59:16.220-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:16.220-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:21.220Z 2016-03-09T00:59:16.220-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:16.220-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:21.220Z 2016-03-09T00:59:16.221-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:16.221-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:21.221Z 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:18.284-0500 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:17.717-0500 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:17.842-0500 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:17.976-0500 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:17.717-0500 2016-03-09T00:59:19.706-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:27.717-0500 2016-03-09T00:59:21.222-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:26.222Z 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:26.223Z 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:26.223Z 2016-03-09T00:59:21.223-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:21.224-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:26.223Z 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:31.225Z 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:31.225Z 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:26.225-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:31.225Z 2016-03-09T00:59:26.226-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:26.226-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:31.226Z 2016-03-09T00:59:27.717-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:26.295-0500 2016-03-09T00:59:27.718-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:25.729-0500 2016-03-09T00:59:27.718-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:25.852-0500 2016-03-09T00:59:27.718-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:25.987-0500 2016-03-09T00:59:27.718-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:25.729-0500 2016-03-09T00:59:27.718-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:35.729-0500 2016-03-09T00:59:31.227-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:31.227-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:36.227Z 2016-03-09T00:59:31.227-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:31.227-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:36.227Z 2016-03-09T00:59:31.227-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:31.228-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:36.227Z 2016-03-09T00:59:31.229-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:31.229-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:36.229Z 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:34.307-0500 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:33.741-0500 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:33.861-0500 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:33.996-0500 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:33.741-0500 2016-03-09T00:59:35.729-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:43.741-0500 2016-03-09T00:59:36.230-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:36.230-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:41.230Z 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:41.231Z 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:41.231Z 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:36.231-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:41.231Z 2016-03-09T00:59:41.233-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:41.233-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:46.233Z 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:46.234Z 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:46.234Z 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:41.234-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:46.234Z 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:42.319-0500 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:41.754-0500 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:41.869-0500 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:42.006-0500 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:41.754-0500 2016-03-09T00:59:43.742-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:51.754-0500 2016-03-09T00:59:46.235-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:46.235-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:51.235Z 2016-03-09T00:59:46.236-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:46.236-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:51.236Z 2016-03-09T00:59:46.236-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:46.236-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:51.236Z 2016-03-09T00:59:46.237-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:46.237-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:51.237Z 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T05:59:56.238Z 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T05:59:56.238Z 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:51.238-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T05:59:56.238Z 2016-03-09T00:59:51.239-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:51.239-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T05:59:56.239Z 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:50.330-0500 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:49.766-0500 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:49.880-0500 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:50.015-0500 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:49.766-0500 2016-03-09T00:59:51.754-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T00:59:59.766-0500 2016-03-09T00:59:56.240-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T00:59:56.241-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:01.240Z 2016-03-09T00:59:56.241-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T00:59:56.241-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:01.241Z 2016-03-09T00:59:56.241-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T00:59:56.241-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:01.241Z 2016-03-09T00:59:56.242-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T00:59:56.242-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:01.242Z 2016-03-09T00:59:59.766-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:58.341-0500 2016-03-09T00:59:59.767-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:57.779-0500 2016-03-09T00:59:59.767-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:57.893-0500 2016-03-09T00:59:59.767-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T00:59:58.025-0500 2016-03-09T00:59:59.767-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T00:59:57.779-0500 2016-03-09T00:59:59.767-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:07.779-0500 2016-03-09T01:00:01.243-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:06.243Z 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:06.244Z 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:06.244Z 2016-03-09T01:00:01.244-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:01.245-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:06.244Z 2016-03-09T01:00:06.246-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:06.246-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:11.246Z 2016-03-09T01:00:06.246-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:06.247-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:11.246Z 2016-03-09T01:00:06.247-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:06.247-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:11.247Z 2016-03-09T01:00:06.247-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:06.247-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:11.247Z 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:06.352-0500 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:05.790-0500 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:05.904-0500 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:06.035-0500 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:05.790-0500 2016-03-09T01:00:07.779-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:15.790-0500 2016-03-09T01:00:11.248-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:11.248-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:16.248Z 2016-03-09T01:00:11.249-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:11.249-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:16.249Z 2016-03-09T01:00:11.249-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:11.249-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:16.249Z 2016-03-09T01:00:11.250-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:11.250-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:16.250Z 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:14.364-0500 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:13.802-0500 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:13.913-0500 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:14.047-0500 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:13.802-0500 2016-03-09T01:00:15.790-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:23.802-0500 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:21.250Z 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:21.251Z 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:16.251-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:21.251Z 2016-03-09T01:00:16.253-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:16.253-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:21.253Z 2016-03-09T01:00:21.252-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:21.252-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:26.252Z 2016-03-09T01:00:21.253-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:21.253-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:26.253Z 2016-03-09T01:00:21.253-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:21.253-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:26.253Z 2016-03-09T01:00:21.255-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:21.255-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:26.255Z 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:22.376-0500 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:21.814-0500 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:21.924-0500 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:22.058-0500 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:21.814-0500 2016-03-09T01:00:23.802-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:31.814-0500 2016-03-09T01:00:26.255-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:26.255-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:31.255Z 2016-03-09T01:00:26.256-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:26.256-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:31.256Z 2016-03-09T01:00:26.256-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:26.256-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:31.256Z 2016-03-09T01:00:26.259-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:26.259-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:31.259Z 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:36.258Z 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:36.259Z 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:31.259-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:36.259Z 2016-03-09T01:00:31.261-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:31.262-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:36.261Z 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:30.387-0500 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:29.826-0500 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:29.936-0500 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:30.065-0500 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:29.826-0500 2016-03-09T01:00:31.814-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:39.826-0500 2016-03-09T01:00:36.260-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:36.261-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:41.260Z 2016-03-09T01:00:36.262-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:36.262-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:41.262Z 2016-03-09T01:00:36.262-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:36.262-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:41.262Z 2016-03-09T01:00:36.263-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:36.263-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:41.263Z 2016-03-09T01:00:39.826-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:38.398-0500 2016-03-09T01:00:39.827-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:37.838-0500 2016-03-09T01:00:39.827-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:37.947-0500 2016-03-09T01:00:39.827-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:38.074-0500 2016-03-09T01:00:39.827-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:37.838-0500 2016-03-09T01:00:39.827-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:47.838-0500 2016-03-09T01:00:41.262-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:41.262-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:46.262Z 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:46.265Z 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:46.265Z 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:41.265-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:46.265Z 2016-03-09T01:00:46.264-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:46.264-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:51.264Z 2016-03-09T01:00:46.266-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:46.266-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:51.266Z 2016-03-09T01:00:46.267-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:46.267-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:51.267Z 2016-03-09T01:00:46.267-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:46.267-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:51.267Z 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:46.409-0500 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:45.850-0500 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:45.955-0500 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:46.086-0500 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:45.850-0500 2016-03-09T01:00:47.838-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:00:55.850-0500 2016-03-09T01:00:51.267-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:51.267-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:00:56.267Z 2016-03-09T01:00:51.268-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:51.268-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:00:56.268Z 2016-03-09T01:00:51.269-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:51.269-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:00:56.269Z 2016-03-09T01:00:51.270-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:51.270-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:00:56.270Z 2016-03-09T01:00:55.850-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:54.421-0500 2016-03-09T01:00:55.851-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:53.862-0500 2016-03-09T01:00:55.851-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:53.965-0500 2016-03-09T01:00:55.851-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:00:54.096-0500 2016-03-09T01:00:55.851-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:00:53.862-0500 2016-03-09T01:00:55.851-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:03.862-0500 2016-03-09T01:00:56.269-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:00:56.269-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:01.269Z 2016-03-09T01:00:56.270-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:00:56.270-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:01.270Z 2016-03-09T01:00:56.270-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:00:56.270-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:01.270Z 2016-03-09T01:00:56.273-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:00:56.273-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:01.273Z 2016-03-09T01:01:01.272-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:01.272-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:06.272Z 2016-03-09T01:01:01.273-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:01.273-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:06.273Z 2016-03-09T01:01:01.273-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:01.273-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:06.273Z 2016-03-09T01:01:01.275-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:01.275-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:06.275Z 2016-03-09T01:01:03.862-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:02.432-0500 2016-03-09T01:01:03.863-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:01.875-0500 2016-03-09T01:01:03.863-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:01.975-0500 2016-03-09T01:01:03.863-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:02.106-0500 2016-03-09T01:01:03.863-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:01:01.875-0500 2016-03-09T01:01:03.863-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:11.875-0500 2016-03-09T01:01:06.274-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:06.275-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:11.274Z 2016-03-09T01:01:06.275-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:06.275-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:11.275Z 2016-03-09T01:01:06.275-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:06.275-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:11.275Z 2016-03-09T01:01:06.277-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:06.277-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:11.277Z 2016-03-09T01:01:11.276-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:11.276-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:16.276Z 2016-03-09T01:01:11.277-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:11.277-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:16.277Z 2016-03-09T01:01:11.277-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:11.277-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:16.277Z 2016-03-09T01:01:11.279-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:11.279-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:16.279Z 2016-03-09T01:01:11.875-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:10.443-0500 2016-03-09T01:01:11.876-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:09.889-0500 2016-03-09T01:01:11.876-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:09.986-0500 2016-03-09T01:01:11.876-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:10.118-0500 2016-03-09T01:01:11.876-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:01:09.889-0500 2016-03-09T01:01:11.876-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:19.889-0500 2016-03-09T01:01:16.278-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:16.279-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:21.278Z 2016-03-09T01:01:16.279-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:16.280-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:21.279Z 2016-03-09T01:01:16.280-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:16.280-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:21.280Z 2016-03-09T01:01:16.282-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:16.282-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:21.281Z 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:18.454-0500 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:17.900-0500 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:18.947-0500 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:18.985-0500 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:01:17.900-0500 2016-03-09T01:01:19.889-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:27.900-0500 2016-03-09T01:01:20.753-0500 I NETWORK [conn8] end connection 192.168.200.3:55309 (4 connections now open) 2016-03-09T01:01:21.281-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:21.281-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state PRIMARY 2016-03-09T01:01:21.281-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:26.280Z 2016-03-09T01:01:21.282-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:21.282-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:26.282Z 2016-03-09T01:01:21.283-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:21.283-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:26.283Z 2016-03-09T01:01:21.284-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:21.284-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:26.284Z 2016-03-09T01:01:23.949-0500 I NETWORK [initandlisten] connection accepted from 192.168.200.3:55324 #14 (5 connections now open) 2016-03-09T01:01:26.283-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:26.283-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:31.283Z 2016-03-09T01:01:26.284-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.1:27017 2016-03-09T01:01:26.284-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:01:26.284-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:26.284-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:31.284Z 2016-03-09T01:01:26.285-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:26.285-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:31.285Z 2016-03-09T01:01:26.288-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.1:27017 2016-03-09T01:01:26.289-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:26.289-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state SECONDARY 2016-03-09T01:01:26.289-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:31.289Z 2016-03-09T01:01:27.900-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:26.289-0500 2016-03-09T01:01:27.901-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:27.467-0500 2016-03-09T01:01:27.901-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:26.285-0500 2016-03-09T01:01:27.901-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:26.764-0500 2016-03-09T01:01:27.901-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:01:26.285-0500 2016-03-09T01:01:27.901-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:36.285-0500 2016-03-09T01:01:31.286-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:31.286-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:36.286Z 2016-03-09T01:01:31.286-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:31.287-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:36.286Z 2016-03-09T01:01:31.287-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:31.287-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:36.287Z 2016-03-09T01:01:31.291-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:31.291-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:36.291Z 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:34.468-0500 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:34.479-0500 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:32.778-0500 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:34.777-0500 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:01:32.778-0500 2016-03-09T01:01:36.285-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:42.778-0500 2016-03-09T01:01:36.286-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.4:27017 2016-03-09T01:01:36.286-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:01:36.289-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:36.289-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state PRIMARY 2016-03-09T01:01:36.289-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:41.289Z 2016-03-09T01:01:36.289-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:36.289-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:41.289Z 2016-03-09T01:01:36.290-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.4:27017 2016-03-09T01:01:36.291-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:36.291-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state SECONDARY 2016-03-09T01:01:36.291-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:41.291Z 2016-03-09T01:01:36.293-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:36.293-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:41.292Z 2016-03-09T01:01:41.291-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:41.291-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:46.291Z 2016-03-09T01:01:41.292-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:41.292-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:46.292Z 2016-03-09T01:01:41.294-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:41.294-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:46.294Z 2016-03-09T01:01:41.294-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:41.294-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:46.294Z 2016-03-09T01:01:42.778-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:41.473-0500 2016-03-09T01:01:42.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:42.490-0500 2016-03-09T01:01:42.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:37.781-0500 2016-03-09T01:01:42.779-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:39.780-0500 2016-03-09T01:01:42.779-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:01:37.781-0500 2016-03-09T01:01:42.779-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:47.781-0500 2016-03-09T01:01:46.292-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.2:27017 2016-03-09T01:01:46.293-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:46.296-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state PRIMARY 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:51.295Z 2016-03-09T01:01:46.296-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.2:27017 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:51.296Z 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:46.296-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:51.296Z 2016-03-09T01:01:46.297-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:46.297-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state SECONDARY 2016-03-09T01:01:46.297-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:51.297Z 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:44.497-0500 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:46.495-0500 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:45.910-0500 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:44.783-0500 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T01:01:44.497-0500 2016-03-09T01:01:47.781-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:54.497-0500 2016-03-09T01:01:51.297-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:51.297-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:01:56.297Z 2016-03-09T01:01:51.298-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:51.298-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:01:56.298Z 2016-03-09T01:01:51.299-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:51.299-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:01:56.299Z 2016-03-09T01:01:51.300-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:51.300-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:01:56.300Z 2016-03-09T01:01:54.497-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:49.498-0500 2016-03-09T01:01:54.498-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:51.498-0500 2016-03-09T01:01:54.498-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:53.919-0500 2016-03-09T01:01:54.498-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:51.298-0500 2016-03-09T01:01:54.498-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T01:01:49.498-0500 2016-03-09T01:01:54.498-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:01:59.498-0500 2016-03-09T01:01:56.298-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.3:27017 2016-03-09T01:01:56.299-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.3:27017 2016-03-09T01:01:56.299-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:01:56.301-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:01:56.301-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:01.301Z 2016-03-09T01:01:56.301-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.3:27017 2016-03-09T01:01:56.302-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:01:56.302-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state PRIMARY 2016-03-09T01:01:56.302-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:01.302Z 2016-03-09T01:01:56.302-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:01:56.303-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:01.302Z 2016-03-09T01:01:56.303-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:01:56.303-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state SECONDARY 2016-03-09T01:01:56.303-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:01.303Z 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:59.306-0500 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:56.500-0500 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:57.925-0500 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:01:55.929-0500 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] earliest member 3 date: 2016-03-09T01:01:55.929-0500 2016-03-09T01:01:59.499-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:05.929-0500 2016-03-09T01:02:01.303-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:01.304-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:06.303Z 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:06.305Z 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:06.305Z 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:01.305-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:06.305Z 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:05.312-0500 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:05.508-0500 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:02.929-0500 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:00.933-0500 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] earliest member 3 date: 2016-03-09T01:02:00.933-0500 2016-03-09T01:02:05.930-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:10.933-0500 2016-03-09T01:02:06.306-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:06.306-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:11.306Z 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:11.307Z 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:11.307Z 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:06.307-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:11.307Z 2016-03-09T01:02:10.933-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:09.318-0500 2016-03-09T01:02:10.934-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:09.322-0500 2016-03-09T01:02:10.934-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:07.932-0500 2016-03-09T01:02:10.934-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:09.328-0500 2016-03-09T01:02:10.934-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:02:07.932-0500 2016-03-09T01:02:10.934-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:17.932-0500 2016-03-09T01:02:11.307-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.1:27017 2016-03-09T01:02:11.308-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:02:11.309-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:11.309-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:16.309Z 2016-03-09T01:02:11.309-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:11.309-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state PRIMARY 2016-03-09T01:02:11.309-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:16.309Z 2016-03-09T01:02:11.311-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:11.311-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:16.311Z 2016-03-09T01:02:11.311-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.1:27017 2016-03-09T01:02:11.313-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:11.313-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state SECONDARY 2016-03-09T01:02:11.313-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:16.313Z 2016-03-09T01:02:16.312-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:16.312-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:21.312Z 2016-03-09T01:02:16.313-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:16.313-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:21.313Z 2016-03-09T01:02:16.313-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:16.313-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:21.313Z 2016-03-09T01:02:16.315-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:16.315-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:21.315Z 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:16.322-0500 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:14.325-0500 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:16.313-0500 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:17.338-0500 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:02:14.325-0500 2016-03-09T01:02:17.933-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:24.325-0500 2016-03-09T01:02:21.313-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.4:27017 2016-03-09T01:02:21.314-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:02:21.316-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:21.316-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state PRIMARY 2016-03-09T01:02:21.316-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:26.316Z 2016-03-09T01:02:21.316-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:21.317-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:26.316Z 2016-03-09T01:02:21.317-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:21.317-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:26.317Z 2016-03-09T01:02:21.317-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.4:27017 2016-03-09T01:02:21.318-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:21.318-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state SECONDARY 2016-03-09T01:02:21.318-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:26.318Z 2016-03-09T01:02:24.325-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:21.324-0500 2016-03-09T01:02:24.326-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:23.051-0500 2016-03-09T01:02:24.326-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:19.345-0500 2016-03-09T01:02:24.326-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:21.344-0500 2016-03-09T01:02:24.326-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:02:19.345-0500 2016-03-09T01:02:24.326-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:29.345-0500 2016-03-09T01:02:26.319-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:26.319-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:31.319Z 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:31.320Z 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:31.320Z 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:26.320-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:31.320Z 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:28.329-0500 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:29.058-0500 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:24.347-0500 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:26.346-0500 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:02:24.347-0500 2016-03-09T01:02:29.345-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:34.347-0500 2016-03-09T01:02:31.320-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.2:27017 2016-03-09T01:02:31.320-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:36.323Z 2016-03-09T01:02:31.323-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.2:27017 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:31.323-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state PRIMARY 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:36.323Z 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:31.323-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:36.323Z 2016-03-09T01:02:31.324-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:31.324-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state SECONDARY 2016-03-09T01:02:31.324-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:36.324Z 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:31.066-0500 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:33.065-0500 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:34.095-0500 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:31.349-0500 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T01:02:31.066-0500 2016-03-09T01:02:34.347-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:41.066-0500 2016-03-09T01:02:36.326-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:36.326-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:41.326Z 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:41.327Z 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:41.327Z 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:36.327-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:41.327Z 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:41.059-0500 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:38.068-0500 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:40.103-0500 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:40.358-0500 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:02:38.068-0500 2016-03-09T01:02:41.066-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:48.068-0500 2016-03-09T01:02:41.329-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:41.329-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:46.329Z 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:46.330Z 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:46.330Z 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:41.330-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state PRIMARY 2016-03-09T01:02:41.330-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:46.330Z 2016-03-09T01:02:46.331-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.3:27017 2016-03-09T01:02:46.332-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:02:46.332-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:46.333-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:51.332Z 2016-03-09T01:02:46.333-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:46.333-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:51.333Z 2016-03-09T01:02:46.335-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:46.335-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:51.335Z 2016-03-09T01:02:46.335-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.3:27017 2016-03-09T01:02:46.336-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:46.336-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state SECONDARY 2016-03-09T01:02:46.336-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:51.336Z 2016-03-09T01:02:48.068-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:47.067-0500 2016-03-09T01:02:48.068-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:46.333-0500 2016-03-09T01:02:48.069-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:46.336-0500 2016-03-09T01:02:48.069-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:47.113-0500 2016-03-09T01:02:48.069-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:02:46.333-0500 2016-03-09T01:02:48.069-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:02:56.333-0500 2016-03-09T01:02:51.334-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:51.334-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:02:56.334Z 2016-03-09T01:02:51.335-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:51.335-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:02:56.335Z 2016-03-09T01:02:51.337-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:51.338-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:02:56.337Z 2016-03-09T01:02:51.338-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:51.338-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:02:56.338Z 2016-03-09T01:02:56.333-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:55.078-0500 2016-03-09T01:02:56.333-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:53.080-0500 2016-03-09T01:02:56.334-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:54.113-0500 2016-03-09T01:02:56.334-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:54.891-0500 2016-03-09T01:02:56.334-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:02:53.080-0500 2016-03-09T01:02:56.334-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:03.080-0500 2016-03-09T01:02:56.336-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:02:56.336-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state PRIMARY 2016-03-09T01:02:56.337-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:01.336Z 2016-03-09T01:02:56.337-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.1:27017 2016-03-09T01:02:56.337-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:02:56.338-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:02:56.338-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:01.338Z 2016-03-09T01:02:56.340-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.1:27017 2016-03-09T01:02:56.340-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:02:56.340-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:01.340Z 2016-03-09T01:02:56.341-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:02:56.342-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state SECONDARY 2016-03-09T01:02:56.342-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:01.341Z 2016-03-09T01:03:01.339-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:01.339-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:06.339Z 2016-03-09T01:03:01.340-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:01.341-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:06.340Z 2016-03-09T01:03:01.342-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:01.342-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:06.342Z 2016-03-09T01:03:01.343-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:01.343-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:06.343Z 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:00.081-0500 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:02:58.081-0500 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:01.118-0500 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:02.904-0500 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:02:58.081-0500 2016-03-09T01:03:03.080-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:08.081-0500 2016-03-09T01:03:06.339-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.4:27017 2016-03-09T01:03:06.339-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:03:06.342-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:06.342-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state PRIMARY 2016-03-09T01:03:06.342-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:11.342Z 2016-03-09T01:03:06.343-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.4:27017 2016-03-09T01:03:06.344-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:06.344-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:11.344Z 2016-03-09T01:03:06.344-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:06.344-0500 I REPL [ReplicationExecutor] Member 192.168.200.4:27017 is now in state SECONDARY 2016-03-09T01:03:06.344-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:11.344Z 2016-03-09T01:03:06.346-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:06.346-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:11.345Z 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:06.346-0500 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:07.433-0500 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:04.912-0500 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:06.911-0500 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:03:04.912-0500 2016-03-09T01:03:08.081-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:14.912-0500 2016-03-09T01:03:11.345-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:11.345-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:16.345Z 2016-03-09T01:03:11.346-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:11.347-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:16.346Z 2016-03-09T01:03:11.347-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:11.347-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:16.347Z 2016-03-09T01:03:11.348-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:11.348-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:16.348Z 2016-03-09T01:03:14.912-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:14.090-0500 2016-03-09T01:03:14.912-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:13.440-0500 2016-03-09T01:03:14.912-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:09.915-0500 2016-03-09T01:03:14.912-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:11.914-0500 2016-03-09T01:03:14.912-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:03:09.915-0500 2016-03-09T01:03:14.913-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:19.915-0500 2016-03-09T01:03:16.347-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:16.347-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:21.347Z 2016-03-09T01:03:16.348-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:16.349-0500 I REPL [ReplicationExecutor] Member 192.168.200.3:27017 is now in state PRIMARY 2016-03-09T01:03:16.349-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:21.348Z 2016-03-09T01:03:16.350-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:16.350-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:21.350Z 2016-03-09T01:03:16.350-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:16.350-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:21.350Z 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:17.452-0500 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:19.451-0500 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:19.503-0500 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:16.917-0500 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] earliest member 3 date: 2016-03-09T01:03:16.917-0500 2016-03-09T01:03:19.916-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:26.917-0500 2016-03-09T01:03:21.347-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.2:27017 2016-03-09T01:03:21.347-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:03:21.350-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:21.350-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:26.350Z 2016-03-09T01:03:21.350-0500 I ASIO [NetworkInterfaceASIO-Replication-0] Successfully connected to 192.168.200.2:27017 2016-03-09T01:03:21.353-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:21.353-0500 I REPL [ReplicationExecutor] Member 192.168.200.2:27017 is now in state SECONDARY 2016-03-09T01:03:21.353-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:26.353Z 2016-03-09T01:03:21.353-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:21.353-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:26.353Z 2016-03-09T01:03:21.354-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:21.354-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:26.354Z 2016-03-09T01:03:26.353-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:2, msg: 2016-03-09T01:03:26.353-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:31.353Z 2016-03-09T01:03:26.356-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:3, msg: 2016-03-09T01:03:26.356-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:31.356Z 2016-03-09T01:03:26.356-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:26.356-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:31.356Z 2016-03-09T01:03:26.357-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:26.357-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:31.357Z 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:22.455-0500 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:24.453-0500 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:25.512-0500 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:25.924-0500 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] earliest member 0 date: 2016-03-09T01:03:22.455-0500 2016-03-09T01:03:26.917-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:32.455-0500 2016-03-09T01:03:28.576-0500 I NETWORK [conn7] end connection 192.168.200.4:47946 (4 connections now open) 2016-03-09T01:03:28.982-0500 I NETWORK [conn14] end connection 192.168.200.3:55324 (3 connections now open) 2016-03-09T01:03:31.354-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.3:27017 2016-03-09T01:03:31.355-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:03:31.356-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.356-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:03:31.356-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:31.356Z 2016-03-09T01:03:31.357-0500 I ASIO [ReplicationExecutor] dropping unhealthy pooled connection to 192.168.200.4:27017 2016-03-09T01:03:31.357-0500 I ASIO [ReplicationExecutor] after drop, pool was empty, going to spawn some connections 2016-03-09T01:03:31.358-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.358-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:31.358-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:31.358Z 2016-03-09T01:03:31.358-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.358-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 4ms have already elapsed 2016-03-09T01:03:31.358-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:31.358Z 2016-03-09T01:03:31.358-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:31.359-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:36.358Z 2016-03-09T01:03:31.359-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:31.359-0500 I REPL [ReplicationExecutor] Member 192.168.200.1:27017 is now in state PRIMARY 2016-03-09T01:03:31.359-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:36.359Z 2016-03-09T01:03:31.359-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.359-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:31.359-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:36.359Z 2016-03-09T01:03:31.360-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.360-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:03:31.360-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:31.359Z 2016-03-09T01:03:31.361-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:31.361-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:31.361-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:36.361Z 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:31.000-0500 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:31.359-0500 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:27.515-0500 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:27.519-0500 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] earliest member 2 date: 2016-03-09T01:03:27.515-0500 2016-03-09T01:03:32.456-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:37.515-0500 2016-03-09T01:03:36.361-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.361-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:03:36.362-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:36.361Z 2016-03-09T01:03:36.362-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:36.362-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:41.362Z 2016-03-09T01:03:36.362-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:36.362-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:41.362Z 2016-03-09T01:03:36.363-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.363-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 4ms have already elapsed 2016-03-09T01:03:36.363-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:36.363Z 2016-03-09T01:03:36.363-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.363-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:36.363-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:36.363Z 2016-03-09T01:03:36.364-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.364-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:36.364-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:41.364Z 2016-03-09T01:03:36.364-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.364-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:03:36.364-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:36.364Z 2016-03-09T01:03:36.365-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:36.365-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:36.365-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:41.365Z 2016-03-09T01:03:37.515-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:37.006-0500 2016-03-09T01:03:37.516-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:36.461-0500 2016-03-09T01:03:37.516-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:27.519-0500 2016-03-09T01:03:37.516-0500 D REPL [ReplicationExecutor] earliest member 3 date: 2016-03-09T01:03:27.519-0500 2016-03-09T01:03:37.516-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:37.519-0500 2016-03-09T01:03:37.519-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:37.006-0500 2016-03-09T01:03:37.519-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:36.461-0500 2016-03-09T01:03:37.519-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:03:36.461-0500 2016-03-09T01:03:37.519-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:46.461-0500 2016-03-09T01:03:41.365-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:41.365-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:46.365Z 2016-03-09T01:03:41.366-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:41.366-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:46.366Z 2016-03-09T01:03:41.366-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.366-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:03:41.366-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:41.366Z 2016-03-09T01:03:41.367-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.367-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:03:41.367-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:41.367Z 2016-03-09T01:03:41.367-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.367-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:03:41.367-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:41.367Z 2016-03-09T01:03:41.368-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.368-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:03:41.368-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:41.368Z 2016-03-09T01:03:41.368-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.368-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:41.368-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:46.368Z 2016-03-09T01:03:41.369-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:41.369-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:41.369-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:46.369Z 2016-03-09T01:03:46.369-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:46.369-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:51.369Z 2016-03-09T01:03:46.369-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:46.369-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:51.369Z 2016-03-09T01:03:46.369-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.370-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:46.370-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:46.369Z 2016-03-09T01:03:46.371-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.371-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:03:46.371-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:46.371Z 2016-03-09T01:03:46.371-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.371-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:03:46.371-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:46.371Z 2016-03-09T01:03:46.372-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.372-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:46.372-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:51.372Z 2016-03-09T01:03:46.372-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.372-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:03:46.372-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:46.372Z 2016-03-09T01:03:46.373-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:46.373-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:46.373-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:51.373Z 2016-03-09T01:03:46.461-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:45.015-0500 2016-03-09T01:03:46.461-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:44.471-0500 2016-03-09T01:03:46.461-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:03:44.471-0500 2016-03-09T01:03:46.461-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:03:54.471-0500 2016-03-09T01:03:51.372-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:51.372-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:03:56.372Z 2016-03-09T01:03:51.374-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:51.374-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:03:56.374Z 2016-03-09T01:03:51.375-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.375-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 3ms have already elapsed 2016-03-09T01:03:51.375-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:51.375Z 2016-03-09T01:03:51.375-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.375-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:51.375-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:51.375Z 2016-03-09T01:03:51.376-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.376-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 4ms have already elapsed 2016-03-09T01:03:51.376-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:51.376Z 2016-03-09T01:03:51.377-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.377-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:03:51.377-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:51.377Z 2016-03-09T01:03:51.377-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.377-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:51.377-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:56.377Z 2016-03-09T01:03:51.378-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:51.378-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:51.378-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:56.378Z 2016-03-09T01:03:54.472-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:53.025-0500 2016-03-09T01:03:54.472-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:03:52.479-0500 2016-03-09T01:03:54.472-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:03:52.479-0500 2016-03-09T01:03:54.472-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:02.479-0500 2016-03-09T01:03:56.376-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:03:56.376-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:01.376Z 2016-03-09T01:03:56.377-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:03:56.377-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:01.377Z 2016-03-09T01:03:56.378-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.378-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:56.378-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:56.378Z 2016-03-09T01:03:56.379-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.379-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:03:56.379-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:03:56.379Z 2016-03-09T01:03:56.379-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.379-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:03:56.379-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:56.379Z 2016-03-09T01:03:56.380-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.380-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:03:56.380-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:01.380Z 2016-03-09T01:03:56.380-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.380-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:03:56.380-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:03:56.380Z 2016-03-09T01:03:56.381-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:03:56.381-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:03:56.381-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:01.381Z 2016-03-09T01:04:01.380-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:01.380-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:06.380Z 2016-03-09T01:04:01.381-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:01.381-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:06.381Z 2016-03-09T01:04:01.382-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.382-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:01.382-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:01.382Z 2016-03-09T01:04:01.382-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.382-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:01.382-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:01.382Z 2016-03-09T01:04:01.383-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.383-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:01.383-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:01.383Z 2016-03-09T01:04:01.383-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.383-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:04:01.383-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:01.383Z 2016-03-09T01:04:01.384-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.384-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:01.384-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:06.384Z 2016-03-09T01:04:01.385-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:01.385-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:01.385-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:06.385Z 2016-03-09T01:04:02.479-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:01.035-0500 2016-03-09T01:04:02.479-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:00.491-0500 2016-03-09T01:04:02.479-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:00.491-0500 2016-03-09T01:04:02.479-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:10.491-0500 2016-03-09T01:04:06.383-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:06.383-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:11.383Z 2016-03-09T01:04:06.383-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:06.383-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:11.383Z 2016-03-09T01:04:06.386-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.386-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:06.386-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:06.386Z 2016-03-09T01:04:06.386-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.386-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:06.386-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:06.386Z 2016-03-09T01:04:06.387-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.387-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:04:06.387-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:06.387Z 2016-03-09T01:04:06.387-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.387-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:04:06.387-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:06.387Z 2016-03-09T01:04:06.388-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.388-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:06.388-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:11.388Z 2016-03-09T01:04:06.388-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:06.388-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:06.388-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:11.388Z 2016-03-09T01:04:10.491-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:09.046-0500 2016-03-09T01:04:10.492-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:08.503-0500 2016-03-09T01:04:10.492-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:08.503-0500 2016-03-09T01:04:10.492-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:18.503-0500 2016-03-09T01:04:11.386-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:11.386-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:16.386Z 2016-03-09T01:04:11.386-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:11.386-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:16.386Z 2016-03-09T01:04:11.390-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.390-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:11.390-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:11.390Z 2016-03-09T01:04:11.390-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.390-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:11.390-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:11.390Z 2016-03-09T01:04:11.391-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.391-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:11.391-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:11.391Z 2016-03-09T01:04:11.391-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.391-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:04:11.391-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:11.391Z 2016-03-09T01:04:11.392-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.392-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:11.392-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:16.392Z 2016-03-09T01:04:11.392-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:11.393-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:11.393-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:16.392Z 2016-03-09T01:04:16.389-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:16.389-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:21.389Z 2016-03-09T01:04:16.390-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:16.390-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:21.390Z 2016-03-09T01:04:16.393-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.394-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:16.394-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:16.393Z 2016-03-09T01:04:16.394-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.394-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:16.394-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:16.394Z 2016-03-09T01:04:16.395-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.395-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:16.395-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:16.395Z 2016-03-09T01:04:16.395-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.395-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:16.395-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:16.395Z 2016-03-09T01:04:16.396-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.396-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:16.396-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:21.396Z 2016-03-09T01:04:16.396-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:16.396-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:16.396-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:21.396Z 2016-03-09T01:04:18.503-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:17.055-0500 2016-03-09T01:04:18.504-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:16.515-0500 2016-03-09T01:04:18.504-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:16.515-0500 2016-03-09T01:04:18.504-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:26.515-0500 2016-03-09T01:04:21.392-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:21.392-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:26.391Z 2016-03-09T01:04:21.393-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:21.393-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:26.393Z 2016-03-09T01:04:21.397-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.397-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:21.397-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:21.397Z 2016-03-09T01:04:21.397-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.398-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:21.398-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:21.397Z 2016-03-09T01:04:21.399-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.399-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:21.399-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:21.399Z 2016-03-09T01:04:21.399-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.399-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:21.399-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:21.399Z 2016-03-09T01:04:21.400-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.400-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:21.400-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:26.400Z 2016-03-09T01:04:21.400-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:21.400-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:21.400-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:26.400Z 2016-03-09T01:04:26.394-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:26.394-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:31.394Z 2016-03-09T01:04:26.395-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:26.395-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:31.395Z 2016-03-09T01:04:26.402-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.402-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:26.402-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:26.402Z 2016-03-09T01:04:26.402-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.402-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:26.402-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:26.402Z 2016-03-09T01:04:26.403-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.403-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:26.403-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:26.403Z 2016-03-09T01:04:26.403-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.403-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:26.403-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:26.403Z 2016-03-09T01:04:26.404-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.404-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:26.404-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:31.404Z 2016-03-09T01:04:26.404-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:26.404-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:26.404-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:31.404Z 2016-03-09T01:04:26.515-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:25.065-0500 2016-03-09T01:04:26.515-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:24.527-0500 2016-03-09T01:04:26.515-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:24.527-0500 2016-03-09T01:04:26.515-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:34.527-0500 2016-03-09T01:04:31.397-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:31.397-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:36.397Z 2016-03-09T01:04:31.398-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:31.398-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:36.398Z 2016-03-09T01:04:31.406-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.406-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:31.406-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:31.406Z 2016-03-09T01:04:31.406-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.406-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:31.406-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:31.406Z 2016-03-09T01:04:31.407-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.407-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:31.407-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:31.407Z 2016-03-09T01:04:31.407-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.407-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:31.407-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:31.407Z 2016-03-09T01:04:31.408-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.408-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:31.408-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:36.408Z 2016-03-09T01:04:31.408-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:31.408-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:31.408-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:36.408Z 2016-03-09T01:04:34.528-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:33.074-0500 2016-03-09T01:04:34.528-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:32.538-0500 2016-03-09T01:04:34.528-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:32.538-0500 2016-03-09T01:04:34.528-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:42.538-0500 2016-03-09T01:04:36.400-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:36.400-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:41.400Z 2016-03-09T01:04:36.401-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:36.401-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:41.401Z 2016-03-09T01:04:36.410-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.410-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:36.410-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:36.410Z 2016-03-09T01:04:36.410-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.410-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:36.410-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:36.410Z 2016-03-09T01:04:36.411-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.411-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:36.411-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:36.411Z 2016-03-09T01:04:36.411-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.411-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:36.411-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:36.411Z 2016-03-09T01:04:36.412-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.412-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:36.412-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:41.412Z 2016-03-09T01:04:36.412-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:36.412-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:36.412-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:41.412Z 2016-03-09T01:04:41.403-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:41.403-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:46.403Z 2016-03-09T01:04:41.403-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:41.403-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:46.403Z 2016-03-09T01:04:41.413-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.413-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:41.413-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:41.413Z 2016-03-09T01:04:41.413-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.413-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 1ms have already elapsed 2016-03-09T01:04:41.414-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:41.413Z 2016-03-09T01:04:41.414-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.414-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 2ms have already elapsed 2016-03-09T01:04:41.414-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:41.414Z 2016-03-09T01:04:41.415-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.415-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:41.415-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:41.415Z 2016-03-09T01:04:41.415-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.416-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:41.416-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:46.415Z 2016-03-09T01:04:41.416-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:41.416-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:41.416-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:46.416Z 2016-03-09T01:04:42.539-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:41.084-0500 2016-03-09T01:04:42.539-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:40.550-0500 2016-03-09T01:04:42.539-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:40.550-0500 2016-03-09T01:04:42.539-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:50.550-0500 2016-03-09T01:04:46.406-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:1, msg: 2016-03-09T01:04:46.406-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.2:27017 at 2016-03-09T06:04:51.406Z 2016-03-09T01:04:46.407-0500 D REPL [ReplicationExecutor] setUpValues: heartbeat response good for member _id:0, msg: 2016-03-09T01:04:46.407-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.1:27017 at 2016-03-09T06:04:51.407Z 2016-03-09T01:04:46.417-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.417-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:46.417-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:46.417Z 2016-03-09T01:04:46.418-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.418-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 1; 2ms have already elapsed 2016-03-09T01:04:46.418-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:46.418Z 2016-03-09T01:04:46.418-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.418-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.3:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:46.418-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:46.418Z 2016-03-09T01:04:46.419-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.3:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.419-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:2, msg: Connection refused 2016-03-09T01:04:46.419-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.3:27017 at 2016-03-09T06:04:51.419Z 2016-03-09T01:04:46.419-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.419-0500 D REPL [ReplicationExecutor] Bad heartbeat response from 192.168.200.4:27017; trying again; Retries left: 0; 3ms have already elapsed 2016-03-09T01:04:46.419-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:46.419Z 2016-03-09T01:04:46.420-0500 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.200.4:27017; HostUnreachable: Connection refused 2016-03-09T01:04:46.420-0500 D REPL [ReplicationExecutor] setDownValues: heartbeat response failed for member _id:3, msg: Connection refused 2016-03-09T01:04:46.420-0500 D REPL [ReplicationExecutor] Scheduling heartbeat to 192.168.200.4:27017 at 2016-03-09T06:04:51.420Z 2016-03-09T01:04:50.550-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:49.093-0500 2016-03-09T01:04:50.551-0500 D REPL [ReplicationExecutor] slaveinfo lastupdate is: 2016-03-09T01:04:48.562-0500 2016-03-09T01:04:50.551-0500 D REPL [ReplicationExecutor] earliest member 1 date: 2016-03-09T01:04:48.562-0500 2016-03-09T01:04:50.551-0500 D REPL [ReplicationExecutor] scheduling next check at 2016-03-09T01:04:58.562-0500