In recent versions of 3.1.x, an idle replica set will emit slow query messages for getMores on the primary:
m31000| 2015-07-29T13:26:11.359-0400 I COMMAND [conn10] command local.oplog.rs command: getMore { getMore: 22205584705, collection: "oplog.rs", maxTimeMS: 2000 } ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:1 reslen:86 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, oplog: { acquireCount: { r: 3 } } } protocol:op_command 2001ms m31000| 2015-07-29T13:26:11.359-0400 I COMMAND [conn11] command local.oplog.rs command: getMore { getMore: 21801738166, collection: "oplog.rs", maxTimeMS: 2000 } ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:1 reslen:86 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, oplog: { acquireCount: { r: 3 } } } protocol:op_command 2001ms m31000| 2015-07-29T13:26:13.361-0400 I COMMAND [conn11] command local.oplog.rs command: getMore { getMore: 21801738166, collection: "oplog.rs", maxTimeMS: 2000 } ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:1 reslen:86 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, oplog: { acquireCount: { r: 3 } } } protocol:op_command 2000ms ...
Potential issues here:
1 - Idle replica sets shouldn't be so chatty (3.0.5 is much less verbose)
2 - awaitData information seems to be missing from the log messages
- is related to
-
SERVER-19307 Use find/getmore commands in bgsync thread
- Closed
- links to