[SERVER-32120] Node sends multiple heartbeats to same node milliseconds apart Created: 29/Nov/17  Updated: 06/Dec/22  Resolved: 20/Feb/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Replication
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

Nodes shouldn't schedule multiple heartbeats to the same node milliseconds apart:

[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.023+0000 d22516| 2017-11-24T04:55:32.021+0000 D REPL_HB  [replexec-5] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:32.021Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.027+0000 d22516| 2017-11-24T04:55:32.023+0000 D REPL_HB  [replexec-7] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:32.023Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.031+0000 d22516| 2017-11-24T04:55:32.025+0000 D REPL_HB  [replexec-3] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:32.525Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.530+0000 d22516| 2017-11-24T04:55:32.526+0000 D REPL_HB  [replexec-3] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:32.526Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.536+0000 d22516| 2017-11-24T04:55:32.528+0000 D REPL_HB  [replexec-4] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:32.528Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:32.542+0000 d22516| 2017-11-24T04:55:32.529+0000 D REPL_HB  [replexec-1] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.029Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.051+0000 d22516| 2017-11-24T04:55:33.031+0000 D REPL_HB  [replexec-1] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.031Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.056+0000 d22516| 2017-11-24T04:55:33.034+0000 D REPL_HB  [replexec-6] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.034Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.060+0000 d22516| 2017-11-24T04:55:33.036+0000 D REPL_HB  [replexec-0] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.536Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.540+0000 d22516| 2017-11-24T04:55:33.538+0000 D REPL_HB  [replexec-0] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.538Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.545+0000 d22516| 2017-11-24T04:55:33.539+0000 D REPL_HB  [replexec-2] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:33.539Z
[js_test:read_committed_after_rollback] 2017-11-24T04:55:33.548+0000 d22516| 2017-11-24T04:55:33.543+0000 D REPL_HB  [replexec-5] Scheduling heartbeat to ip-10-65-177-159:22510 at 2017-11-24T04:55:34.043Z



 Comments   
Comment by Gregory McKeon (Inactive) [ 07/Feb/18 ]

judah.schvimer should this go back to needs triage?

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