ephraimbuddy commented on issue #10026: URL: https://github.com/apache/airflow/issues/10026#issuecomment-899302193
> I have started seeing the same issue since migrating to Airflow 2.1 when clearing task states, never had it with Airflow 2.0.1 🤔 > > ``` > INFO 2021-05-27 15:40:20,582 airflow.task.task_runner.standard_task_runner.StandardTaskRunner Started process 17792 to run task > INFO 2021-05-27 15:40:20,587 airflow.task.task_runner.standard_task_runner.StandardTaskRunner Job 51280: Subtask XXXX > INFO 2021-05-27 15:40:28,885 airflow.task Running <TaskInstance: XXX.XXXX 2020-01-12T00:00:00+00:00 [running]> on host airflow-d88cdb6b6-9lg6t > WARNING 2021-05-27 15:40:29,640 airflow.jobs.local_task_job.LocalTaskJob Recorded pid 4304 does not match the current pid 17792 > INFO 2021-05-27 15:40:29,642 airflow.task.task_runner.standard_task_runner.StandardTaskRunner Sending Signals.SIGTERM to GPID 17792 > INFO 2021-05-27 15:40:29,649 airflow.task.task_runner.standard_task_runner.StandardTaskRunner Process psutil.Process(pid=17792, status='terminated', exitcode=<Negsignal.SIGTERM: -15>, started='15:40:20') (17792) terminated with exit code Negsignal.SIGTERM > ``` > > It seems to happen when many tasks are to be scheduled, I suspect maybe a DB concurrency issue? Maybe something similar to #15714 ? But I am not sure why it never happened before I suspect you cleared these tasks when they were still running. I have added a PR for a case I reproduced when deleting running DAGs from the UI #17630 -- 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]
