Uploaded image for project: 'Apache Airflow'
  1. Apache Airflow
  2. AIRFLOW-39

DagRun scheduled after end_date

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.7.0
    • None
    • None
    • None
    • - Airflow version: v1.7.0
      - Airflow components: webserver and scheduler with a postgres database and LocalExecutor
      - Python Version: 2.7.9

    Description

      Hello

      When I write a new DAG, it is automatically picked by the scheduler as intended. However the end_date parameter is not accounted when creating a DagRun, so that DagRuns scheduled after end_date are being displayed in the web interface and are staying in the running state forever as the scheduler doesn't launch them.

      From my reading of the sources, the end_date paremeter is not used when creating a DagRun.

      Is there any reason for this behaviour ?

      Regards
      dud

      Attachments

        1. tutorial4.png
          57 kB
          dud
        2. tutorial4_grpah.png
          53 kB
          dud
        3. Tree_view_only_shows_runs_within_start_end_range.png
          100 kB
          Siddharth Anand
        4. Task_instance_view_only_shows_TIs_within_start_end_range.png
          275 kB
          Siddharth Anand
        5. Jobs_view_only_shows_runs_within_start_end_range.png
          218 kB
          Siddharth Anand
        6. Head_master_dag_runs_past_date_failed.png
          245 kB
          Siddharth Anand
        7. 1_7_0_dag_runs_past_date_running.png
          279 kB
          Siddharth Anand

        Activity

          People

            sanand Siddharth Anand
            dud dud
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: