potiuk commented on issue #18422: URL: https://github.com/apache/airflow/issues/18422#issuecomment-1030877597
I have no ide where the default comes from - but maybe you passed it in the operator? The HttpOperator has "extra_options" dictionary that you can pass "requests" parameters (including "timeout" mentioned in the docuementation). Maybe - unknowingly - you pass a value there. You can also pass a None value to force "no timeout" https://docs.python-requests.org/en/latest/user/advanced/#timeouts - unfortunately "requests" does not tell explicitly what default it has, so mabe it is somehow server/system dependent. Maybe a variable of some sort. Or maybe this is something in your infrastructure that kills the request after 5 minutes of inactivity ? Airlfow requests are coming from the machine where tasks are running - and this might be inside an infrastructure that you have no access to (so even if it works from your local machine, it might not work if you run it via airflow because it is run elsewhere. This usually happens on various deployments when you have firewals/corporate environment. In this case I am afraid you neeed to talk to your infra people. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
