CHANGELOG: set dates for 3.1.12 & 3.2.17 release #9414
Conversation
CHANGELOG-3.1.md
Outdated
|
|
||
| ### Improved | ||
|
|
||
| - Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9364) to reduce [disruptive rejoining servers](https://github.com/coreos/etcd/issues/9333). |
There was a problem hiding this comment.
@gyuho Should this go all the way back to 3.1?
There was a problem hiding this comment.
Yeah, I'm fine with backporting to 3.1.
There was a problem hiding this comment.
Original issue from @wojtek-t was running 3.1 https://groups.google.com/forum/#!msg/etcd-dev/82bPTmzGVM0/EiTINb6dBQAJ.
Codecov Report
@@ Coverage Diff @@
## master #9414 +/- ##
=========================================
Coverage ? 72.34%
=========================================
Files ? 362
Lines ? 30795
Branches ? 0
=========================================
Hits ? 22280
Misses ? 6891
Partials ? 1624Continue to review full report at Codecov.
|
CHANGELOG-3.1.md
Outdated
|
|
||
| - Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9364) to reduce [disruptive rejoining servers](https://github.com/coreos/etcd/issues/9333). | ||
| - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node. | ||
| - Now, when etcd restarts, it does not fast-forward election ticks. |
There was a problem hiding this comment.
Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
#9415 is merged, where it adjust election ticks on restart.
There was a problem hiding this comment.
Updated CHANGELOGs to use reference #9415
CHANGELOG-3.2.md
Outdated
|
|
||
| - Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9364) to reduce [disruptive rejoining servers](https://github.com/coreos/etcd/issues/9333). | ||
| - Previously, etcd fast-forwards election ticks on server start, with only one tick left for leader election. This is to speed up start phase, without having to wait until all election ticks elapse. Advancing election ticks is useful for cross datacenter deployments with larger election timeouts. However, it was affecting cluster availability if the last tick elapses before leader contacts the restarted node. | ||
| - Now, when etcd restarts, it does not fast-forward election ticks. |
There was a problem hiding this comment.
Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
#9415 is merged, where it adjust election ticks on restart.
There was a problem hiding this comment.
Oh I meant
Now, when etcd restarts, it does not fast-forward election ticks.
is not true anymore.
When #9415 is merged, then it works as
Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart.
There was a problem hiding this comment.
Sorry, I follow now. CHANGELOGs fixed.
a537828 to
34b6a12
Compare
34b6a12 to
c032c7c
Compare
c032c7c to
4017eca
Compare
|
When do we expect v3.1.13 to be released? |
|
We have one more pending fix. Hopefully sometime next week. |
And add notes in preparation of 3.1.13 and 3.2.18