-
Notifications
You must be signed in to change notification settings - Fork 71
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
aiohttp: Response payload is not completed #235
Comments
Thanks for reporting the issue. Could you send information about your cluster - K8s version, cloud provider? |
Now using k8s version 1.19 soon will add newer versions. We are developing cloud, now it is in closed beta testing. |
I am also facing this issue, will this be fixed? |
Unfortunately I'm not able to recreate the issue. @vishnukv-facets could you share more details about your case - your cluster type, k8s version, what kind of interfaces you are watching etc. Thanks. |
Had the same problem: All Job's above 60 seconds failed in a async with kubernetes_asyncio.watch.Watch() as w:
async for event in w.stream(...)
... with Our setup: kubernetes I found this issue in the aiohttp GitHub repo. One of the answers made me believe that we are facing the same issue with our kubernetes setup. The ha-proxy has its own timeout set (for us at 50 seconds). So all our jobs taking more than 50 seconds receive the error. (this is due to the fact that the proxy kills all requests which do not send any data for some time and since the Fixed it by using a Alternatively, you probably could increase the timeout of the proxy (in the case for the ha proxy, configure it in the |
After about 3 minutes I got an error:
aiohttp.client_exceptions.ClientPayloadError: Response payload is not completed
Run:
python: 3.7.2 and 3.9.12
kubernetes_asyncio: 18.20.0 and 24.2.2
The text was updated successfully, but these errors were encountered: