[SERVER-22523] investigate liveness timeout resetting Created: 08/Feb/16  Updated: 18/Nov/16  Resolved: 11/Feb/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.1
Fix Version/s: 3.2.3, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-22153 Cancelling heartbeats doesn't work af... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Participants:

 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.



 Comments   
Comment by Githook User [ 11/Feb/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-22523: disable warning msg when multiple heartbeats are active/returning

(cherry picked from commit c35b85eb3adb92d6bfc20fcbe66e915d88f1b4d4)
Branch: v3.2
https://github.com/mongodb/mongo/commit/3a2816a72a92ecbcf9244210cfa403f972e10317

Comment by Githook User [ 11/Feb/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-22523: disable warning msg when multiple heartbeats are active/returning
Branch: master
https://github.com/mongodb/mongo/commit/537f6040894eb4bbfb44063daa4f7314ba82d7d6

Generated at Thu Feb 08 04:00:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.