dabla commented on issue #45930: URL: https://github.com/apache/airflow/issues/45930#issuecomment-2607539721
> Should we apply this logic for the underlying get hook function that we are using? While not generic to all if we can provide workaround for connections that support it I think we should. Yet the underlying issue is not clear to me. The kill signal from timeout comes from the scheduler. Why would the task not respond to it? The `exectuion_timeout` is for Airflow, not for the underlying SQL engine. We could, but that possibly would not work for all cases and would be a workaround of the real issue. It's indeed a weird issue and I was also surprised by that behaviour. Back then I thought it was related to the Jdbc connection and maybe there was some glitch between the Python and Java process, but now we can assume this is a generic issue related to database connections. So yes it's weird that worker doesn't get killed. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org