Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resetted nodes were briefly identified as alive. #133

Merged
merged 1 commit into from
Feb 28, 2024

Conversation

fulmicoton
Copy link
Contributor

The reason is that we call report_heartbeat in the reset procedure. The purpose of this call is to make sure that we have a record in the failure detector for the node.

This PR just creates the failure detector entry, and avoid recording a heartbeat change.

This PR also makes sure we do not count the first heartbeat record as an event.

Closes #132

The reason is that we call report_heartbeat in the reset procedure.
The purpose of this call is to make sure that we have a record in the failure detector for the node.

This PR just creates the failure detector entry, and avoid recording a
heartbeat change.

This PR also makes sure we do not count the first heartbeat record as an event.

Closes #132
@fulmicoton fulmicoton requested review from trinity-1686a and guilload and removed request for trinity-1686a February 28, 2024 14:06
@fulmicoton fulmicoton marked this pull request as ready for review February 28, 2024 14:06
@fulmicoton fulmicoton merged commit 867207e into main Feb 28, 2024
2 checks passed
@fulmicoton fulmicoton deleted the issue/132-bugfix-resetted-nodes-marked-as-alive-b branch February 28, 2024 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid identifying resetted dead nodes as alive
2 participants