trlopes1974 commented on issue #39717:
URL: https://github.com/apache/airflow/issues/39717#issuecomment-2211612922

   some more info:
   
   Despite that we do have an external task id
   **Dependencies Blocking Task From Getting Scheduled
   Dependency | Reason
   Dagrun Running | Task instance's dagrun was not in the 'running' state but 
in the state 'failed'.
   ...
   external_executor_id | 4f9de4af-fba0-4d6a-852e-3a82d32bc721**
   
   It does not appear in flower, so it seems that it never got into celery (in 
tis case).
   
   also, in this case, the time lag between this faileds task and its "sister" 
task is 10minutes  (task_adoption_timeout = 600)
   
![image](https://github.com/apache/airflow/assets/16724800/44b3c1ce-d745-4971-8fe9-a5d31673a129)
   These 2 tasks run at the same time
   
   1st task log:
   *** Found local files:
   ***   * 
/opt/tkapp/airflow/logs/dag_id=CSDISPATCHER_OTHERS/run_id=scheduled__2024-07-05T15:37:00+00:00/task_id=dispatch_restores/attempt=1.log
   **[2024-07-05, 16:42:11 WEST]** {taskinstance.py:1042} DEBUG - 
previous_execution_date was called
   
   
   2nd task log:
   *** Found local files:
   ***   * 
/opt/tkapp/airflow/logs/dag_id=CSDISPATCHER_OTHERS/run_id=scheduled__2024-07-05T15:37:00+00:00/task_id=dispatch_correcao_dados/attempt=1.log.SchedulerJob.log
   **[2024-07-05, 16:52:37 WEST]** {event_scheduler.py:40} WARNING - Marking 
task instance <TaskInstance: CSDISPATCHER_OTHERS.dispatch_correcao_dados 
scheduled__2024-07-05T15:37:00+00:00 [queued]> stuck in queued as failed. If 
the task instance has available retries, it will be retried.
   [2024-07-05, 16:52:37 WEST] {scheduler_job_runner.py:843} ERROR - Executor 
reports task instance <TaskInstance: 
CSDISPATCHER_OTHERS.dispatch_correcao_dados 
scheduled__2024-07-05T15:37:00+00:00 [queued]> finished (failed) although the 
task says it's queued. (Info: None) Was the task killed externally?
   
   
   


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