You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/09/02 18:09:02 UTC

[jira] [Commented] (AIRFLOW-2404) Message for why a DAG run has not been scheduled missing information

    [ https://issues.apache.org/jira/browse/AIRFLOW-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601626#comment-16601626 ] 

Apache Spark commented on AIRFLOW-2404:
---------------------------------------

User 'AetherUnbound' has created a pull request for this issue:
https://github.com/apache/incubator-airflow/pull/3286

> Message for why a DAG run has not been scheduled missing information
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-2404
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2404
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webserver
>            Reporter: Matthew Bowden
>            Assignee: Matthew Bowden
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The webserver lists the following reasons for why a DAG run/task instance might not be started:
>  * The scheduler is down or under heavy load
>  * This task instance already ran and had its state changed manually (e.g. cleared in the UI)
> Another reason that the task might not have been started is because of the following:
>  * The {{parallelism}} configuration value may be too low
>  * The {{dag_concurrency}} configuration value may be too low
>  * The {{max_active_dag_runs_per_dag}} configuration value may be too low
>  * The {{non_pooled_task_slot_count}} configuration value may be too low



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)