History

yuzhiquanlong 4c13767881 etcdserver: add alarms metrics for server Signed-off-by: yuzhiquanlong <yuzhiquanlong@gmail.com>		2022-08-03 09:33:02 +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	update changelog-3.4 to protection for rangePermCache with a RW lock	2022-07-24 23:34:05 +09:00
CHANGELOG-3.5.md	update changelog-3.5 to protection for rangePermCache with a RW lock	2022-07-18 00:22:01 +09:00
CHANGELOG-3.6.md	etcdserver: add alarms metrics for server	2022-08-03 09:33:02 +08:00
CHANGELOG-4.0.md	sync-changelog: /health break change was reverted	2022-06-24 14:57:05 +08:00
README.md	Update production recommendation for v3.5.3	2022-04-13 21:55:56 +02:00

README.md

Production recommendation

The minimum recommended etcd versions to run in production are 3.3.18+, 3.4.2+, v3.5.3+. 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.3.

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