-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
EOF errors from reqwest .next() #146
Comments
Wondering if this is related to #144 and us doing something wrong in the request_events loop by not stopping correctly. The EOF error seems to originate from hyper in https://github.com/hyperium/hyper/blob/6b47c69f4a0c67ef416a492cc129ae1955c659f6/src/proto/h1/decode.rs#L101-L127, and it's just coming straight out of the Unless there's an underlying bug in reqwest, I'd imagine this is would only happen if we tried to carry on too much in the unfold. |
I can see it happening when the watch times out completely (300s no events):
|
Can be fixed by setting a hard |
This is primarily due to kubernetes/kubernetes#6513 We should have our timeout slightly less than 5 minutes whereas now we have 300s and that's just too much. The issue appears to go away if we hard timeout the client (in the client builder) to 295s, and disallow listparams.timeout >= 295. We should probably still ignore eof errors in the unfold so will try to add that as well. Should also include reqwest bump for #144 |
Fixed in #145 (kube 0.26.0) |
Seeing a lot more of:
I don't remember them happening this frequently. Anyone else seeing this with reflectors?
The text was updated successfully, but these errors were encountered: