schattian commented on issue #23497: URL: https://github.com/apache/airflow/issues/23497#issuecomment-1318967988
fyi @potiuk @swalkowski after investigating a bit more this issue, seems there's a walkaround by using the kubernetes executor. Using celery executor means that the job status is not updated till the pid that observes the execution finishes (execution which hangs by the logs api) Using k8s executor, the status is updated based on pod status instead so it does not hang (as pod status was always updated correctly, but job wasnt) Im trying it but so far it's working, will update. -- 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]
