Re: [D] Some tasks in mapped tasks fail before starting, logs are empty [airflow]

2024-11-21 Thread via GitHub


GitHub user PowerToThePeople111 edited a comment on the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

Ok, observing it even further, I found that exactly the tasks 1,3 and 4 which 
have been initially queued, but not been executed, are now marked as "up for 
retry" and will probably fail later on. My hunge is, that if your 
max_active_tis_per_dagrun is bigger than the number of workers that can be 
spawned (I guess infra started to limit me ;) ) to actually run in parallel, 
this can cause mapped tasks to fail.

My current approach is to set max_active_tis_per_dagrun to 1, forcing airflow 
to do things step by step.

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341297


This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org



Re: [D] Some tasks in mapped tasks fail before starting, logs are empty [airflow]

2024-11-21 Thread via GitHub


GitHub user PowerToThePeople111 added a comment to the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

Ok, observing it even further, I found that exactly the tasks 1,3 and 4 which 
have been initially queued, but not been executed, are now marked as "up for 
retry" and will probably fail later on. My hunge is, that if your 
max_active_tis_per_dagrun is bigger than the number of workers that can be 
spawned (I guess infra started to limit me ;) ) to actually run in parallel, 
this can cause mapped tasks to fail.

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341297


This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org



Re: [D] Some tasks in mapped tasks fail before starting, logs are empty [airflow]

2024-11-21 Thread via GitHub


GitHub user PowerToThePeople111 added a comment to the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

![Bildschirmfoto 2024-11-21 um 21 51 
47](https://github.com/user-attachments/assets/7338f6c4-35ad-4980-8c39-75e1ecdb78d2)
This is a screenshot of the run I do atm.

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341200


This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org



Re: [D] Some tasks in mapped tasks fail before starting, logs are empty [airflow]

2024-11-21 Thread via GitHub


GitHub user PowerToThePeople111 edited a comment on the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

I experienced the same. Without sharing the exact code, I can say, that my dag 
is just a chain of sequential virtualenv tasks. The first one is mapped and 
exhibits the same problem as the issue-starter: some mapped tasks are in failed 
state although they have no start or end date.  Also they do not even try to be 
re-executed: although retries are possible, they failed finally already on 
their first try.

Another also strange thing I observed is, that initially there are 4 mapped 
tasks (1-4) queued. But instead of taking one of those initially mapped tasks 
as a second one to process, it will just take another one (the 5th) leaving the 
other ones waiting. Could it be, that this is causing the issue: like some kind 
of time out?

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341165


This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org



Re: [D] Some tasks in mapped tasks fail before starting, logs are empty [airflow]

2024-11-21 Thread via GitHub


GitHub user PowerToThePeople111 added a comment to the discussion: Some tasks 
in mapped tasks fail before starting, logs are empty

I experienced the same. Without sharing the exact code, I can say, that my dag 
is just a chain of sequential virtualenv tasks. The first one is mapped and 
exhibits the same problem as the issue-starter: some mapped tasks are in failed 
state although they have no start or end date.  Also they do not even try to be 
re-executed: although retries are possible, they failed finally already on 
their first try.

GitHub link: 
https://github.com/apache/airflow/discussions/42039#discussioncomment-11341165


This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org