mirror of https://github.com/etcd-io/etcd.git synced 2024-09-27 06:25:44 +00:00

History

Benjamin Wang e4cfa07d09 Update both 3.4 and 3.5 changelog to cover two fixes

Two fixes:
1. netutil: add url comparison without resolver to URLStringsEqual
2. client/v3: Add backoff before retry when watch stream returns unavailable

Signed-off-by: Benjamin Wang <wachao@vmware.com>

2022-10-13 08:29:45 +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 both 3.4 and 3.5 changelog to cover two fixes

2022-10-13 08:29:45 +08:00

CHANGELOG-3.5.md

Update both 3.4 and 3.5 changelog to cover two fixes

2022-10-13 08:29:45 +08:00

CHANGELOG-3.6.md

Update changelog 3.6 to clearly requiring applications which depend on etcd 3.6 packages must be built with go version >= 1.18

2022-10-05 22:56:40 +08:00

CHANGELOG-4.0.md

CHANGELOG: update version recommendation

2022-08-05 20:26:13 -04:00

README.md

changelog: update the recommended version to 3.5.4+

2022-09-14 15:53:14 +08: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.4+.

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