-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Heartbeat improvements and handling failures during establishing leadership #3890
Conversation
Fix a bug in which if the node attributes/meta changed, we would re-register the node in status initializing. This would incorrectly trigger the client to log that it missed its heartbeat. It would change the status of the Node to initializing until the next heartbeat occured.
…ing leadership establishment
Needs hashicorp/consul#3908 to be merged so it can be vendored |
nomad/heartbeat.go
Outdated
// the race in which leadership is lost but a timer is created on this | ||
// server since it was servicing an RPC during a leadership loss. | ||
if !s.IsLeader() { | ||
return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we log a message here, just to indicate that this happened?
LGTM! |
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
The changes in this PR are a result of going through logs of a cluster quickly transition between leaders. As such there are various semi-related fixes:
Fixes #3035
Fixes #3840