eladkal opened a new issue, #24045:
URL: https://github.com/apache/airflow/issues/24045

   ### Body
   
   Currently both DagRun and TaskInstance use queue as state (which is not 
related one to another at all)
   ![Screen Shot 2022-05-31 at 12 38 
44](https://user-images.githubusercontent.com/45845474/171168036-bd6a5995-835b-4f3f-8ca9-084a80f846da.png)
   ![Screen Shot 2022-05-31 at 12 39 
22](https://user-images.githubusercontent.com/45845474/171168042-631e59e1-263a-4160-b454-d88ae7a533dc.png)
   
   
   I find that this is very confusing! because Queue DagRun actually means that 
the DagRun didn’t even start while queue task means it passed the scheduler and 
waiting for worker slot.
   
   
   My suggestion simply not to use the same string (queue) to describe the 
different meaning.
   
   (*) We also use Running for both DagRuns/tasks but I find this specific one 
less confusing as it actually means quite the same (something in worker is 
being executed).
   
   ### Committer
   
   - [X] I acknowledge that I am a maintainer/committer of the Apache Airflow 
project.


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to