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
update raft to v1.3.8 #12844
update raft to v1.3.8 #12844
Conversation
.changelog/12844.txt
Outdated
@@ -0,0 +1,3 @@ | |||
```release-note:bug | |||
raft: upgrade to v1.3.6 which fixes a bug where non cluster member can still be able to participate in an election. |
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 this be v1.3.7
?
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.
good catch, I made a typo writing it
.changelog/12844.txt
Outdated
@@ -0,0 +1,3 @@ | |||
```release-note:bug | |||
raft: upgrade to v1.3.6 which fixes a bug where non cluster member can still be able to participate in an election. |
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.
raft: upgrade to v1.3.6 which fixes a bug where non cluster member can still be able to participate in an election. | |
raft: upgrade to v1.3.7 which fixes a bug where non cluster member can still be able to participate in an election. |
I'm curious, what are the implications of making these fields "reloadable"? (edit) I missed that part of the description. I'm now wondering if something needs to change in Consul to validate updates to these values? |
Also, it looks like |
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.
Approved assuming the changelog is updated as Evan pointed out.
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/650650. |
* update raft to v1.3.7 * add changelog * fix compilation error * fix HeartbeatTimeout * fix ElectionTimeout to reload only if value is valid * fix default values for `ElectionTimeout` and `HeartbeatTimeout` * fix test defaults * bump raft to v1.3.8
This update raft to v1.3.7
In this raft release
HeartbeatTimeout
andElectionTimeout
became reloadable config, so Consul needed to be tweaked to only reload those configs only when the given values are within the acceptable range.Note that this also introduce hashicorp/raft#477