kcphila commented on issue #18041: URL: https://github.com/apache/airflow/issues/18041#issuecomment-1163125103
Hi all, From the discussion over at [issue 17507](https://github.com/apache/airflow/issues/17507), I may have identified issue when the SIGTERM is sent with the **Recorded pid<> does not match the current pid <>** error, but I'm running `LocalExecutor` and not kubernetes. For me, I think this is happening when `RUN_AS_USER` is set for a task *and* the heartbeat is checked when the task instance pid is not set (None). In these cases, the `recorded_pid` gets set to the parent of running task supervisor process, which is Executor itself, instead of the task runner. I don't know if this will address the issue with kubernetes or celery executor, but it seems very likely to be the same issue. It will take me a little while to set up the dev environment and do the testing before submitting a PR, but if you want to try doing a local install, feel free to give it a whirl. I have a tentative branch set up here: https://github.com/krcrouse/airflow/tree/fix-pid-check -- 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]
