Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.2.1
-
Fully Compatible
-
ALL
Description
Under load, a replica set primary logs this message frequently:
[ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
Here's an example log, produced just by running insert_ttl.js from the workloads repo:
2016-02-08T16:52:49.000-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:52:55.308-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:52:57.213-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:03.431-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:04.781-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:05.944-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:08.472-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:08.611-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:11.104-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
2016-02-08T16:53:11.690-0500 W REPL [ReplicationExecutor] The liveness timeout does not match callback handle, so not resetting it.
|
We should look into fixing the issue that causes this, or suppressing the message.
Attachments
Issue Links
- depends on
-
-
- Closed
-