sania-2912 commented on issue #59602: URL: https://github.com/apache/airflow/issues/59602#issuecomment-3670327706
From my understanding, in Airflow 3.1.5 the webserver attempts to fetch served logs from a specific worker pod hostname (for example `airflow-worker-2...`), which may no longer exist after KEDA scales workers down. Even with `remote_logging=True` and `delete_local_logs=True`, the UI still appears to rely on the worker’s hostname, leading to DNS resolution failures. This behavior did not occur with the same setup on Airflow 2.10, which suggests a possible regression or behavioral change in Airflow 3.x logging. -- 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]
