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 [email protected]. To unsubscribe, please send an email to: [email protected]
