Plans for v3.5.9 release

[serathius]

What would you like to be added?

Issues/PRs planned for the release:

• Updated go to latest patch release 1.19.9 #15821
  • [3.5] Backport updating go to latest patch release 1.19.9  #15822
• Updated go to latest patch release 1.19.9 #15821
  • Backport 15656 to release-3.5 #15815

Issues/PRs that can be postponed to next release:

• Etcd watch stream starvation under high read response load when sharing same connection and TLS is enabled #15402 - blocked on net/http: Stream starvation in http2 priority write scheduler golang/go#58804
• When the election time exceeds the network error #14653
• concurrency.NewSession hang after etcd server is killed with SIGSTOP(19) #14631
• etcd memory usage spikes to unsustainable levels and OOMs #14362
• panic due to race between wal rotation and snapshot #14252
• DB size diverged but kvhash were consistent across 3 nodes #14249
• Possible split-brain & loss of committed write with loss of un-fsynced data #14143
• Stale read with loss of un-fsynced writes #14140
• Memory leak with distributed tracing enabled #13990

Why is this needed?

go1.19.9 (released 2023-05-02) includes three security fixes to the html/template package, as well as bug fixes to the compiler, the runtime, and the crypto/tls and syscall packages. See the Go 1.19.9 milestone on our issue tracker for details.

[serathius]

cc @ahrtr @ptabor @spzala @mitake

[ahrtr]

My understanding is #15402 is already resolved in 3.5.8 by splitting the http and gRPC servers. Eventually in 3.7 or 4.0, etcd will split them by default.

Do you mean that etcd should follow up the http server issue, which is supposed to be resolved by Go team, so that the issue can be resolved even users of etcd do not split http and gRPC servers in etcd 3.4 and 3.5?

[serathius]

Do you mean that etcd should follow up the http server issue, which is supposed to be resolved by Go team, so that the issue can be resolved even users of etcd do not split http and gRPC servers in etcd 3.4 and 3.5?

Yes, we should not require that all users follow etcd changelog and know all the flags. We should provide a proper solution available by default.

[serathius]

Published https://github.com/etcd-io/etcd/releases/tag/v3.5.9