[
https://issues.apache.org/jira/browse/AIRFLOW-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114951#comment-17114951
]
ASF GitHub Bot commented on AIRFLOW-5708:
-----------------------------------------
stale[bot] closed pull request #6379:
URL: https://github.com/apache/airflow/pull/6379
----------------------------------------------------------------
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:
us...@infra.apache.org
> Tasks that use non-existent pools should fail early
> ---------------------------------------------------
>
> Key: AIRFLOW-5708
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5708
> Project: Apache Airflow
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.10.5
> Reporter: Joshua Carp
> Assignee: Joshua Carp
> Priority: Minor
>
> Tasks associated with non-existent pools are never scheduled. The scheduler
> emits a warning log when it encounters these tasks, but there's no
> user-facing warning. I think that tasks with non-existent pools should throw
> an error, and ideally should throw it early. I'm submitting a draft PR to
> optionally cause dag parsing to fail if any task pools don't exist, but I'd
> be open to other approaches too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
