potiuk commented on issue #27555: URL: https://github.com/apache/airflow/issues/27555#issuecomment-1307388470
I don't think this is in "all cases" - I think you have a specific problem that manifests this way - because the workers would usually use `hostname_callable` (https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#hostname-callable) to get their internal name. I suspect what you observe might be the in-famous instabilito of DNS in k8s (which happens quite often adn in some cases it might be even completely broken). I thnk you need to get deeper into seeing what is your problem (follow the hostname_callable lead). It's likely that you will find the root cause by doing it and likely that it might result in a new feature, but I think more details and digging is need on what your problem is. For now I am converting it into a discussion. We can always convert it back to issue or you will be able to open a new one. Also I suggest to try whatever problem you have with latest airflow version 2.4.3 - there have been some improvements in som parts of the hostname_callable handling that might give better diagnostics into what the real problem is. -- 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]
