eladkal commented on code in PR #41593: URL: https://github.com/apache/airflow/pull/41593#discussion_r1722052772
########## docs/apache-airflow/troubleshooting.rst: ########## @@ -20,6 +20,19 @@ Troubleshooting =============== +Obscure scheduling failures Review Comment: I rather we won't place this here. Our goal should be shorting this doc not adding more stuff to it. I rather we explain the mechanisem of scheduler-executor dynamic in the relevant section if the docs and then explain the limits/edge cases. ########## docs/apache-airflow/troubleshooting.rst: ########## @@ -20,6 +20,19 @@ Troubleshooting =============== +Obscure scheduling failures +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +State mismatch between Airflow database and executor +---------------------------------------------------- + +This indicates that when the scheduler queried the Airflow database, it observed that the task instance had one status according to the Airflow metadata database, +but a different status according to the executor. A common example is when the query returned to the scheduler, the task instance was in the ``queued`` status, +but the status according to the executor was ``running``. + +This mismatch must have persisted for multiple attempts. When this happens, Airflow will not attempt to queue the task. It's possible that something has gone wrong Review Comment: Attempts=airflow retries? ########## docs/apache-airflow/troubleshooting.rst: ########## @@ -20,6 +20,19 @@ Troubleshooting =============== +Obscure scheduling failures +^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +State mismatch between Airflow database and executor +---------------------------------------------------- + +This indicates that when the scheduler queried the Airflow database, it observed that the task instance had one status according to the Airflow metadata database, +but a different status according to the executor. A common example is when the query returned to the scheduler, the task instance was in the ``queued`` status, Review Comment: What query? -- 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]
