You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "john-jac (via GitHub)" <gi...@apache.org> on 2023/02/13 18:53:58 UTC

[GitHub] [airflow] john-jac commented on a diff in pull request #29511: Add Landing Times entry to UI docs

john-jac commented on code in PR #29511:
URL: https://github.com/apache/airflow/pull/29511#discussion_r1104894469


##########
docs/apache-airflow/ui.rst:
##########
@@ -160,6 +160,22 @@ DAG over many runs.
 
 ------------
 
+Landing Times
+.............
+Airflow landing times are calculated from the task's scheduled time to 
+the time the task finishes, either with success or another state (see 
+:ref:`concepts:task-instances`).  When subtracting the task duration 
+(above) from the landing time you will find the adoption time.  If the 
+adoption time exceeds the 
+:ref:`task adoption timeout <config:celery__task_adoption_timeout>` 
+then the task will be terminated and, if applicable, rescheduled.

Review Comment:
   Great question @eladkal .  We know this is an important factor for the Celery executor, but I do not think there is an equivalent for other executors.  As such, should I pull this out as a note instead, or perhaps move that part of the comment out of the UI section and into the Celery config section that it references?



-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org