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
Error while watching pods: too old resource version with v2.4.5 #226
Comments
similar error with 2.4.5 on 1.15 |
I have downgraded the plugin to v2.4.1 in fluent-operator Gemfile and I don't see any of these errors from past 2 days. BTW, it is on k8s version 1.16.3. So definitely an issue with 2.4.5 |
It looks like this is addressed in 2.4.6. |
we have the same exact issue with GKE 1.16.8-gke.15. |
I'm seeing the same error with v2.4.6 |
Digging into the "too old resource version" error a bit, I believe the problem lies in the handling of type fluent-plugin-kubernetes_metadata_filter/lib/fluent/plugin/kubernetes_metadata_watch_pods.rb Line 131 in 1b67682
The Kubernetes concepts documentation explains this case and how clients should handle it in this document: https://kubernetes.io/docs/reference/using-api/api-concepts/#efficient-detection-of-changes Here's the relevant excerpt:
|
@jcantrill I suspect that the fix is to add special handling for status code |
The See: https://github.com/abonas/kubeclient#starting-watch-version |
According to the good folks on the kubeclient project, the way to check for the 410 status in the notice is:
|
@jcantrill I've submitted a PR which I believe should solve this problem based on my learnings explained in the comments above. One question for you: Should I include a minor version bump in my PR if I'd like this to go into a new release? Or do the maintainers handle that process yourselves? |
We'll bump the version when we publish |
Awesome. Thanks, @jcantrill. Active maintainers like you are a treasure. |
Error while watching pods: too old resource version: 23630883 (23632006) (RuntimeError)
complete stacktrace
The text was updated successfully, but these errors were encountered: