vitalif
/
etcd
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
etcd/CHANGELOG
History
Benjamin Wang ebfcaaed34 test: fix the test failures in e2e/warning_logging_test.go 
1. Fixed the test failures which are caused by recent test framework rafactoring;
2. renamed the file to promote_experimental_flag_test.go.

Signed-off-by: Benjamin Wang <wachao@vmware.com>
 		2022-11-19 01:51:06 +08:00
..
CHANGELOG-2.3.md Move changelogs to subdirectory 2022-01-26 11:46:20 +01:00
CHANGELOG-3.0.md Move changelogs to subdirectory 2022-01-26 11:46:20 +01:00
CHANGELOG-3.1.md changelog: Update and deduplicate production recommendations 2022-03-29 19:09:01 +02:00
CHANGELOG-3.2.md changelog: Update and deduplicate production recommendations 2022-03-29 19:09:01 +02:00
CHANGELOG-3.3.md changelog: Update and deduplicate production recommendations 2022-03-29 19:09:01 +02:00
CHANGELOG-3.4.md Merge pull request #14794 from cleverhu/fix-max-recv-msg-size-description 2022-11-17 18:05:47 +08:00
CHANGELOG-3.5.md changelog: add items to cover the issue of refreshing token on CommonName based authentication 2022-11-17 09:27:09 +08:00
CHANGELOG-3.6.md test: fix the test failures in e2e/warning_logging_test.go 2022-11-19 01:51:06 +08:00
CHANGELOG-4.0.md CHANGELOG: update version recommendation 2022-08-05 20:26:13 -04:00
README.md Update changelog readme to add rules on how to add changelog items 2022-10-14 10:40:50 +08:00

README.md

Change logs

Production recommendation

The minimum recommended etcd versions to run in production are v3.4.8+ and v3.5.4+. Refer to the versioning policy for more details.

v3.5 data corruption issue

Running etcd v3.5.2, v3.5.1 and v3.5.0 under high load can cause a data corruption issue. If etcd process is killed, occasionally some committed transactions are not reflected on all the members. Recommendation is to upgrade to v3.5.4+.

If you have encountered data corruption, please follow instructions on https://etcd.io/docs/v3.5/op-guide/data_corruption/.

Change log rules

  1. Each patch release only includes changes against previous patch release. For example, the change log of v3.5.5 should only include items which are new to v3.5.4.
  2. For the first release (e.g. 3.4.0, 3.5.0, 3.6.0, 4.0.0 etc.) for each minor or major version, it only includes changes which are new to the first release of previous minor or major version. For example, v3.5.0 should only include items which are new to v3.4.0, and v3.6.0 should only include items which are new to v3.5.0.