potiuk commented on issue #16292:
URL: https://github.com/apache/airflow/issues/16292#issuecomment-856572637
The default setting for timeout is infinite in python/requests/urrlib3
library. I think it's something about your network/connectivity setup. This is
not a client timeout. When you have timeout you get different error ("Read
timed out." or "Network unreachable") - depending if it is a read or connect
timeout. CONNRESET can be caused by a number of things - firewall, proxy,
server timing out the connection. This is usually a deployment issue
I have no idea what deployment you have, but if you are running your Airflow
in GKE then the most likely reason is the stream idle time:
> A Stream idle timeout, whose value is fixed at 5 minutes (300 seconds).
This value is non-configurable. HTTP streams become idle after 5 minutes
without activity.
https://cloud.google.com/load-balancing/docs/l7-internal
And the solution is to set keep-alive < 5 minutes on your server. So not
much Airflow/client can do about it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
