This is an automated email from the ASF dual-hosted git repository.

ephraimanierobi pushed a commit to branch v2-6-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit 900db1bfa71ac9bee9beaf8433c97334b0541798
Author: Ryan Hatter <[email protected]>
AuthorDate: Sat Apr 29 18:18:13 2023 -0400

    Update faq.rst about missing task logs (#30717)
    
    ---------
    
    Co-authored-by: Jed Cunningham 
<[email protected]>
    (cherry picked from commit f3e82b2011faaf2c48ca1258a30de342b2af2cd1)
---
 .../logging-monitoring/logging-tasks.rst                      |  2 ++
 docs/apache-airflow/core-concepts/tasks.rst                   |  1 +
 docs/apache-airflow/faq.rst                                   | 11 +++++++++++
 3 files changed, 14 insertions(+)

diff --git 
a/docs/apache-airflow/administration-and-deployment/logging-monitoring/logging-tasks.rst
 
b/docs/apache-airflow/administration-and-deployment/logging-monitoring/logging-tasks.rst
index 16b2b58e98..495b341e22 100644
--- 
a/docs/apache-airflow/administration-and-deployment/logging-monitoring/logging-tasks.rst
+++ 
b/docs/apache-airflow/administration-and-deployment/logging-monitoring/logging-tasks.rst
@@ -161,6 +161,8 @@ When using remote logging, you can configure Airflow to 
show a link to an extern
 
 Some external systems require specific configuration in Airflow for 
redirection to work but others do not.
 
+.. _serving-worker-trigger-logs:
+
 Serving logs from workers and triggerer
 ---------------------------------------
 
diff --git a/docs/apache-airflow/core-concepts/tasks.rst 
b/docs/apache-airflow/core-concepts/tasks.rst
index dd1cd536a1..faafa29654 100644
--- a/docs/apache-airflow/core-concepts/tasks.rst
+++ b/docs/apache-airflow/core-concepts/tasks.rst
@@ -237,6 +237,7 @@ If you want to control your task's state from within custom 
Task/Operator code,
 
 These can be useful if your code has extra knowledge about its environment and 
wants to fail/skip faster - e.g., skipping when it knows there's no data 
available, or fast-failing when it detects its API key is invalid (as that will 
not be fixed by a retry).
 
+.. _concepts:zombies:
 
 Zombie/Undead Tasks
 -------------------
diff --git a/docs/apache-airflow/faq.rst b/docs/apache-airflow/faq.rst
index bbffd4b333..58defdbdf1 100644
--- a/docs/apache-airflow/faq.rst
+++ b/docs/apache-airflow/faq.rst
@@ -441,6 +441,17 @@ If the tasks are not related by dependency, you will need 
to :ref:`build a custo
 Airflow UI
 ^^^^^^^^^^
 
+Why did my task fail with no logs in the UI?
+--------------------------------------------
+
+Logs are :ref:`typically served when a task reaches a terminal state 
<serving-worker-trigger-logs>`. Sometimes, a task's normal lifecycle is 
disrupted, and the task's
+worker is unable to write the task's logs. This typically happens for one of 
two reasons:
+
+1. :ref:`Zombie tasks <concepts:zombies>`.
+2. Tasks failed after getting stuck in queued (Airflow 2.6.0+). Tasks that are 
in queued for longer than :ref:`scheduler.task_queued_timeout 
<config:scheduler__task_queued_timeout>` will be marked as failed, and there 
will be no task logs in the Airflow UI.
+
+Setting retries for each task drastically reduces the chance that either of 
these problems impact a workflow.
+
 How do I stop the sync perms happening multiple times per webserver?
 --------------------------------------------------------------------
 

Reply via email to