vitalif
/
etcd
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
etcd/CHANGELOG
History
Vitalii Levitskii be58a2539c Added client-auto-sync-interval argument to the grpc-proxy 
Signed-off-by: Vitalii Levitskii <vitalii@uber.com>
 		2022-08-25 15:33:38 +03: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 the release date for 3.4.20 2022-08-06 05:46:51 +08:00
CHANGELOG-3.5.md Update changelog-3.5 to cover the change for refactoring the keepAliveListener and keepAliveConn 2022-08-21 13:06:56 +08:00
CHANGELOG-3.6.md Added client-auto-sync-interval argument to the grpc-proxy 2022-08-25 15:33:38 +03:00
CHANGELOG-4.0.md CHANGELOG: update version recommendation 2022-08-05 20:26:13 -04:00
README.md CHANGELOG: update version recommendation 2022-08-05 20:26:13 -04:00

README.md

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.3.

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