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/05/26 12:46:01 UTC

[GitHub] [airflow] argibbs commented on issue #15596: Using SLAs causes DagFileProcessorManager timeouts and prevents deleted dags from being recreated

argibbs commented on issue #15596:
URL: https://github.com/apache/airflow/issues/15596#issuecomment-848739170


   > @kaxil @ashb Should DAGs deleted via the UI actually be re-added if the file still exists? That seems to defeat the purpose of deleteng
   
   Couple of thoughts on this:
   1. Re-adding the DAG is useful; I consider it functionality equivalent to selecting all existing dag runs and deleting them. If I want the dag gone, I'll remove the underlying file first. Changing this would be a major departure.
   2. The fact the dag is not re-added is (slightly) missing the point. The problem is that the SLAs trigger a feedback loop that prevents the dag processor manager from iterating over all files in a finite time. This means that once this problem is present, _adding_ a new dag is also not picked up until / unless the SLA feedback clears down.


-- 
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:
users@infra.apache.org