-
Notifications
You must be signed in to change notification settings - Fork 38.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kube-apiserver[14274]: E1015 10:17:36.804307 14274 watcher.go:214] watch chan error: etcdserver: mvcc: required revision has been compacted #83938
Comments
Can you post more of the kube-apiserver log (prior to the error) ? Thanks |
It's been exporting like the following logs: Oct 15 16:30:19 node2 kube-apiserver[14274]: I1015 16:30:19.873780 14274 aggregator.go:255] Updating OpenAPI spec because v1beta1.metrics.k8s.io is removed Can I ignore this mistake? Some people say this is the etcd version problem,but when i deployed the kuberntes version 1.15+,there are no longer error logs. Thank you for reply! |
/sig api-machinery |
/assign @wenjiaswe |
etcd is the Kubernetes’ backing store for all cluster data, it has a history compaction mechanism to avoid performance degradation and eventual storage space exhaustion, here are some docs on etcd repo. "watch chan error: etcdserver: mvcc: required revision has been compacted" literally means the watched revision is compacted. This is working as designed, when attempts to re-establish a watch from a resourceVersion that is no longer available would prompt the caller to re-list objects and obtain a new current resourceVersion to watch from.. For your comment "and When I perform "kubectl get cs" it shows "unknown" both etcd and kube-controller-manager and kube-scheduler ", what does that mean? Could you paste the output of "kubectl get cs" here? |
[root@master istio]# kubectl get nodes When I perform "kubectl get cs" it shows "unknown" both etcd and kube-controller-manager and kube-scheduler "。 i have no idea,please give some sugesstions!thanks. |
@wenjiaswe Whats confusing about this message then is that it is logged as an ERROR. If its part of normal operations it should not be logged as an error or probably not logged at all. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Completely agree...the fact that something to be ignored (because it's "working as designed") is being logged as an error should be a red flag for a maintainer of any project, and something to /fix/. EDIT: Appears to be fixed in 1.8 here, #84602 |
Still seeing the same logged as error in the Kube API Server log (kubernetes v1.18.6):
|
do you have do etcd compact Manual? |
That's a "warning", because it has a "W" as the first character. You can also see "I" and "E" lines. |
I´m still seeing these logs in version 1.23.1
|
|
The text was updated successfully, but these errors were encountered: