potiuk edited a comment on issue #18846: URL: https://github.com/apache/airflow/issues/18846#issuecomment-942510109
Then I think you need to do some more checking: a) check if the keep alives are comming (I think you should find out in Postgres logs - they should be coming every 30 seconds). I am sure Postgres logging can be set in the way to show keepalives in logs (but I am not sure how to do it - not a postgres expert) b) look in the logs of Postgres why maybe Postgres itself keeps on closing the connection (if it does close it - I suspected it's a firewall in between). There might be many reasons, memory problem, stale processes, lack of other resources, maximum timeouts set for query and so on. You should at least be ble to correlate the time when Airflow conection was closed and find corresponding log in Postgres server and match them - and maybe you will see who closed the connection (if you see both Postgres and Airflow seeing the "other" party to close the connection - this is likely something in between). c) If you see keepalives coming, and see that both postgres and airflow see the connection killd, I would advise to see if there are maybe other settings in you network that kills an established, long runnning connection with keepalives - some enterprise firewall rules etc - eventually you migh need to involve Azure support to help with finding out what is this. -- 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]
