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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AIRFLOW-2404:
----------------------------------------------------------

Commit 9a0c4e6caeaddde19c2e104d959bdb36b46ab37a in incubator-airflow's branch refs/heads/master from [~AetherUnbound]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=9a0c4e6 ]

[AIRFLOW-2404] Add additional documentation for unqueued task

Closes #3286 from AetherUnbound/feature/task-not-
queued-doc


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