lindsable commented on issue #17693: URL: https://github.com/apache/airflow/issues/17693#issuecomment-915363464
I was just able to confirm that this is still an issue in 2.1.3. I'll update the issue with the logs. The scenario is when a node is removed from the cluster where a worker pod is already scheduled to run. There is an event where the status is still running but the event type is DELETED. In this case I believe we should set the state to up_for_retry. The optimal solution would be to get the name of the new pod from the kubernetes api and follow that one instead, but up_for_retry is better than nothing. -- 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]
