-
Type:
Improvement
-
Resolution: Won't Do
-
Priority:
Major - P3
-
Affects Version/s: 3.3.12
-
Component/s: Replication
-
Labels:None
-
Replication
The current log line looks like:
d20516| 2016-09-02T18:07:43.532+0000 I COMMAND [conn6] command local.oplog.rs command: getMore { getMore: 13838976655, collection: "oplog.rs", maxTimeMS: 5000, term: 2, lastKnownCommittedOpTime: { ts: Timestamp 1472839659000|5, t: 2 } } originatingCommand: { find: "oplog.rs", filter: { ts: { $gte: Timestamp 1472839634000|5 } }, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000, term: 2 } planSummary: COLLSCAN cursorid:13838976655 keysExamined:0 docsExamined:1 numYields:1 nreturned:1 reslen:541 locks:{ Global: { acquireCount: { r: 6 }, acquireWaitCount: { r: 1 }, timeAcquiringMicros: { r: 393 } }, Database: { acquireCount: { r: 3 }, acquireWaitCount: { r: 1 }, timeAcquiringMicros: { r: 107 } }, oplog: { acquireCount: { r: 3 } } } protocol:op_command 4039ms
It'd be nice to include the fromId, so that it's easier to correlate later log lines like:
d20515| 2016-09-02T18:07:53.537+0000 D REPL [rsBackgroundSync] fetcher stopped reading remote oplog on WIN-DE8E6H6F6GH:20516
d20515| 2016-09-02T18:07:53.537+0000 W REPL [rsBackgroundSync] Fetcher error querying oplog: ExceededTimeLimit: Operation timed out, request was RemoteCommand 324 -- target:WIN-DE8E6H6F6GH:20516 db:local expDate:2016-09-02T18:07:53.536+0000 cmd:{ getMore: 13838976655, collection: "oplog.rs", maxTimeMS: 5000, term: 2, lastKnownCommittedOpTime: { ts: Timestamp 1472839659000|6, t: 2 } }
with the first one, because otherwise the entire command must be compared.