You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/09/14 07:02:10 UTC

[GitHub] [airflow] MarvinSchenkel commented on issue #17507: Task processes killed with WARNING - Recorded pid does not match the current pid

MarvinSchenkel commented on issue #17507:
URL: https://github.com/apache/airflow/issues/17507#issuecomment-918867762


   > I will revert also to lastest 2.0 version available: however I do not know what impact it will have on the metadata db (need a downgrade or sth like that) ...
   > 
   > Does someone know if there is an official guide to downgrade ?
   > 
   > So what I did is:
   > 
   > * setup a dedicated postgresql server on Linux for the meta database
   > * downgrade to airflow 2.0.2
   > * increase the heartbeat signal (so that the tasks gets not killed by the heart beat concurrency (mainly for sensors): and will incorporate https://github.com/apache/airflow/pull/16289/files in order to fix the race condition tomorrow.
   > 
   > With this set up my dags are working "properly" (remaining the below bug) ! I no longer have mismatch of pid and no longer have random sigterm on task execution relatively large queries.
   
   How did you increase the heartbeat signal? I am running Airflow on a Kubernetes cluster and run into this issue on 2.1.3, 2.1.2 and 2.0.2. 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org