-
Notifications
You must be signed in to change notification settings - Fork 620
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
HTTP/1.1 header parser received no bytes with k8s and wave #3983
Comments
Full log |
A retry policy has been added to better handle this 👉 1daebee |
It looks like the the cause of this error is a bug in the Http client on Java 17. It should be solved by Java 17.0.7 |
Thanks for looking into this Paolo. I started trying the 23.04.02 release as soon as it came out and thus far it's been looking good... |
More evidence suggests the cause of this issue is the excessive timeout of the connection pool used by the Java HTTP client that by default is 1200 seconds (20 mins!). Changing it to 10 seconds via the following setting it looks like to address the problem
|
Solved by fa961e7 |
Bug report
On two of my pipelines running on EKS/wave/fusion I keep getting a
HTTP/1.1 header parser received no bytes
error that kills the pipeline at different stages of the workflows (non-deterministic). Workflows were working OK until Friday last week.Expected behavior and actual behavior
Pipeline can run processes and retry on errors.
Error is killing entire workflow with a
HTTP/1.1 header parser received no bytes
error.Steps to reproduce the problem
Its a bit difficult to reproduce as pipeline can run OK for about 1-3 hrs but then fail with the
HTTP/1.1 header parser received no bytes
error. Its affecting other workflows so suspect is wave or fusion that might causing problems.Environment
abbreviated log
The text was updated successfully, but these errors were encountered: