Closed agoddard closed 2 years ago
Still happens in 6.6.3
@amdprophet is there anything we can do about this?
@portertech I thought I had managed to reduce it recently but it ended up continuing to happen. I'm not sure if it's possible without a change to etcd.
This ended up being due to streams not being closed by the Etcd clientv3 lessor keepAliveOnce method. I've opened a PR against Etcd with a fix for this https://github.com/etcd-io/etcd/pull/14357.
Moving to next milestone due to uncertainty of etcd release.
https://github.com/etcd-io/etcd/pull/14357 and https://github.com/etcd-io/etcd/pull/14361 merged/closed, can we move forward? Do we have a release to use?
Yes, Etcd v3.5.5 contains the fix. :)
It seems like this can be closed, now that #4878 has been closed?
Indeed. Closed by #4878.
in 6.4.0 we've started logging the following gRPC errors in the backend w/ embedded etcd. They're logged at
debug
level, very verbosely (every 1-2 seconds on a cluster with no agents). Not sure if this is a new issue, or we're now just logging something we previously weren't. Confirmed this behavior doesn't existing 6.3.0 with identical config.