-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance, Networking, Replication
-
None
-
Environment:Linux Debian 7, 8
-
ALL
Running db.adminCommand({ setFeatureCompatibilityVersion: "3.4" }) on replicaset primary gives no feedback, appears to hang.
Possibly related to causing replication failure?
Entry from primary server log after replication cessation:
2016-12-04T23:28:22.399-0600 I NETWORK [conn2985] received client metadata from 10.0.0.10:56185 conn2985: { driver: { name: "NetworkInterfaceASIO-RS", version: "3.4.0" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"", architecture: "x86_64", version: "Kernel 3.2.0-4-amd64" } }
Corresponding entries from one secondary log after replication cessation:
2016-12-05T00:35:40.538-0500 I REPL [replication-24] Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand 380827 -- target:m3.internal.net:27017 db:local expDate:2016-12-05T00:35:40.538-0500 cmd:{ getMore: 35490922038, collection: "oplog.rs", maxTimeMS: 2000 }. Last fetched optime (with hash): { ts: Timestamp 1480915633000|442, t: -1 }[-113046468778785762]. Restarts remaining: 3
2016-12-05T00:35:40.538-0500 I REPL [replication-24] Scheduled new oplog query Fetcher source: m3.internal.net:27017 database: local query: { find: "oplog.rs", filter: { ts: { $gte: Timestamp 1480915633000|442 } }, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000 } query metadata: { $ssm: { $secondaryOk: 1 } } active: 1 timeout: 10000ms inShutdown: 0 first: 1 firstCommandScheduler: RemoteCommandRetryScheduler request: RemoteCommand 380914 -- target:m3.internal.net:27017 db:local cmd:{ find: "oplog.rs", filter: { ts: { $gte: Timestamp 1480915633000|442 } }, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000 } active: 1 callbackHandle.valid: 1 callbackHandle.cancelled: 0 attempt: 1 retryPolicy: RetryPolicyImpl maxAttempts: 1 maxTimeMillis: -1ms