From 4017ecaf0fdb73b3381ffd042ee0348290edd381 Mon Sep 17 00:00:00 2001 From: Joe Betz Date: Thu, 8 Mar 2018 16:09:43 -0800 Subject: [PATCH] CHANGELOG: set dates for 3.1.12 & 3.2.17 releases, add notes for next releases --- CHANGELOG-3.1.md | 14 +++++++++++++- CHANGELOG-3.2.md | 12 +++++++++++- CHANGELOG-3.3.md | 4 ++-- 3 files changed, 26 insertions(+), 4 deletions(-) diff --git a/CHANGELOG-3.1.md b/CHANGELOG-3.1.md index e05d815018c..ec422ad20e0 100644 --- a/CHANGELOG-3.1.md +++ b/CHANGELOG-3.1.md @@ -1,4 +1,16 @@ -## [v3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (TBD) + +## [v3.1.13](https://github.com/coreos/etcd/releases/tag/v3.1.13) (TBD) + +See [code changes](https://github.com/coreos/etcd/compare/v3.1.12...v3.1.13) and [v3.1 upgrade guide](https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) for any breaking changes. + +### Improved + +- Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9415) 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 adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart. + + +## [v3.1.12](https://github.com/coreos/etcd/releases/tag/v3.1.12) (2018-03-08) See [code changes](https://github.com/coreos/etcd/compare/v3.1.11...v3.1.12) and [v3.1 upgrade guide](https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md) for any breaking changes. diff --git a/CHANGELOG-3.2.md b/CHANGELOG-3.2.md index 29fe94cd0ab..710fbda6d4b 100644 --- a/CHANGELOG-3.2.md +++ b/CHANGELOG-3.2.md @@ -1,6 +1,16 @@ +## [v3.2.18](https://github.com/coreos/etcd/releases/tag/v3.2.18) (TBD) -## [v3.2.17](https://github.com/coreos/etcd/releases/tag/v3.2.17) (TBD) +See [code changes](https://github.com/coreos/etcd/compare/v3.2.17...v3.2.18) and [v3.2 upgrade guide](https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes. + +### Improved + +- Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9415) 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 adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart. + + +## [v3.2.17](https://github.com/coreos/etcd/releases/tag/v3.2.17) (2018-03-08) See [code changes](https://github.com/coreos/etcd/compare/v3.2.16...v3.2.17) and [v3.2 upgrade guide](https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_2.md) for any breaking changes. diff --git a/CHANGELOG-3.3.md b/CHANGELOG-3.3.md index 139746198e3..2fe5dbc9d2b 100644 --- a/CHANGELOG-3.3.md +++ b/CHANGELOG-3.3.md @@ -5,9 +5,9 @@ See [code changes](https://github.com/coreos/etcd/compare/v3.3.2...v3.3.3) and [ ### 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). +- Adjust [election timeout on server restart](https://github.com/coreos/etcd/pull/9415) 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. + - Now, when etcd restarts, it adjusts election ticks with more than one tick left, thus more time for leader to prevent disruptive restart. ## [v3.3.2](https://github.com/coreos/etcd/releases/tag/v3.3.2) (2018-03-08)