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/08/15 16:51:53 UTC

[GitHub] [airflow] zhangyi-hu edited a comment on issue #17623: Expose celery config option 'result_expires' to airflow.cfg

zhangyi-hu edited a comment on issue #17623:
URL: https://github.com/apache/airflow/issues/17623#issuecomment-899080607


   **I verified that, by setting the environmental variable `CELERY_RESULT_EXPIRES `, this problem can be solved.** 
   However, the root of this problem is, that whether a task should be rerun is not fully controlled by airflow, unless the user sets this env var as a small number.
   
   To my understanding, the status of a task should be solely managed by airflow. It seems to me that, airflow should always set this celery config as a small value to make celery memoryless, instead of letting the user worry about it.  Does this worth a separate ticket? 


-- 
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