etcdserver: read-only range request "key:\"/registry/services/endpoints/kube-system/kube-scheduler\" " with result "range_response_count:1 size:440" took too long (199.032407ms) to execute

[ibayue]

As shown in the screenshot, this read-only occurs very frequently.

---

Useful	Info
Versions	Rancher v2.2.2 UI: v2.2.41
Route	containers.index

[vishen]

@ibayue we are also seeing this issue on our rancher clusters, did you find the reason or a fix for this?

[loganhz]

link to etcd-io/etcd#10174

[fabiorauber]

I'm also seeing these messages in etcd when the timeouts mentioned in #21587 occur.

[adhomdom]

I was also seeing this, coming from the current rancher:stable image, creating a new cluster on bare-metal. As a result, couldn't register an etcd node.

Downgrading to rancher:v2.2.0 resolved the issue, so I've tagged v2.2.0 in our private repo as stable (didn't use an rc, but accept that I might have trouble upgrading in future).

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.