[
https://issues.apache.org/jira/browse/AIRFLOW-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312252#comment-15312252
]
Jeremiah Lowin commented on AIRFLOW-205:
----------------------------------------
I spoke with [~withnale] -- it sounds like the culprit is the somewhat
confusing workflow of having to run pooled tasks two times (once to queue,
another time to run if a slot is available) rather than a bug.
I'm going to close this issue -- if the "first queue, then run" workflow wasn't
so deeply ingrained in the logic of running tasks, I'd say let's implement a
quick fix. But instead let's make a note that it could be made more
user-friendly in the future. cc [~bolke].
> Unable to force a TaskInstance with a pool assigned to it
> ---------------------------------------------------------
>
> Key: AIRFLOW-205
> URL: https://issues.apache.org/jira/browse/AIRFLOW-205
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Paul Rhodes
> Priority: Minor
>
> It seems that I can force a paused task to run if I select force from the GUI
> but if the job includes a pool that job will never run, even if there is
> space in the pool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
