yuqian90 commented on issue #10790: URL: https://github.com/apache/airflow/issues/10790#issuecomment-727920248
> > The bug can also be fixed if the rescheduled task instance use a different try number, but this will cause a lot of log files. > > I saw customers doing this (custom fork). I'm curious if this error will occur in Airflow 2.0 Hi @turbaszek I did not test this in Airflow 2.0 so I may be wrong. I don't see any attempts to address this in Airflow 2.0 so this is likely going to happen in 2.0 too. That said, the scheduler loop is faster in Airflow 2.0, the chance of running into this `ERROR - Executor reports task instance ... killed externally` issue should become smaller. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
