bertrand-buffat opened a new issue #19329: URL: https://github.com/apache/airflow/issues/19329
### Apache Airflow version 2.1.3 ### Operating System Debian GNU/Linux ### Versions of Apache Airflow Providers apache-airflow-providers-amazon==1.4.0 apache-airflow-providers-cncf-kubernetes==2.0.2 ### Deployment Other 3rd-party Helm chart ### Deployment details _No response_ ### What happened Some tasks are randomly set to Upstream Failed while upstream task actually succeeded ### What you expected to happen I expect downstream tasks to be scheduled ### How to reproduce Failure happens randomly during peak hours of scheduling <img width="643" alt="Screenshot 2021-10-30 at 03 25 08" src="https://user-images.githubusercontent.com/83957187/139540485-a999a119-9ef2-4d02-87a4-007fc1d2c7dd.png"> We use Kubernetes Executor Config for scheduler: [scheduler] job_heartbeat_sec = 5 clean_tis_without_dagrun_interval = 15.0 scheduler_heartbeat_sec = 5 num_runs = -1 processor_poll_interval = 1 min_file_process_interval = 300 dag_dir_list_interval = 300 print_stats_interval = 30 pool_metrics_interval = 5.0 scheduler_health_check_threshold = 30 orphaned_tasks_check_interval = 300.0 child_process_log_directory = /home/airflow/logs/scheduler scheduler_zombie_task_threshold = 300 catchup_by_default = True max_tis_per_query = 512 use_row_level_locking = True max_dagruns_to_create_per_loop = 500 max_dagruns_per_loop_to_schedule = 500 schedule_after_task_execution = True parsing_processes = 8 file_parsing_sort_mode = alphabetical use_job_schedule = True allow_trigger_in_future = False dependency_detector = airflow.serialization.serialized_objects.DependencyDetector run_duration = -1 statsd_port = 8125 statsd_prefix = airflow max_threads = 5 authenticate = False ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
