Closed humit0 closed 2 years ago
@humit0 @andrewdanks @socar-humprey - we have a 2.3.3rc3 (see #24863) that is supposed to handle the Trigger deadlocks - is it possible that you test this version to see if the deadlocks has been fixe with it ? That would be great to get confirmation.
Apache Airflow version
2.2.5
What happened
When create many Deferrable operator (eg.
TimeDeltaSensorAsync
), triggerer component died because of DB Deadlock issue.What you think should happen instead
Triggerer processor does not raise Deadlock error.
How to reproduce
Create "test_timedelta" DAG and run it.
Operating System
uname_result(system='Linux', node='d2845d6331fd', release='5.10.104-linuxkit', version='#1 SMP Thu Mar 17 17:08:06 UTC 2022', machine='x86_64', processor='')
Versions of Apache Airflow Providers
apache-airflow-providers-apache-druid | 2.3.3 apache-airflow-providers-apache-hive | 2.3.2 apache-airflow-providers-apache-spark | 2.1.3 apache-airflow-providers-celery | 2.1.3 apache-airflow-providers-ftp | 2.1.2 apache-airflow-providers-http | 2.1.2 apache-airflow-providers-imap | 2.2.3 apache-airflow-providers-jdbc | 2.1.3 apache-airflow-providers-mysql | 2.2.3 apache-airflow-providers-postgres | 4.1.0 apache-airflow-providers-redis | 2.0.4 apache-airflow-providers-sqlite | 2.1.3 apache-airflow-providers-ssh | 2.4.3
Deployment
Other Docker-based deployment
Deployment details
webserver: 1 instance scheduler: 1 instance worker: 1 instance (Celery) triggerer: 1 instance redis: 1 instance Database: 1 instance (mysql)
Anything else
webserver: 172.19.0.9 scheduler: 172.19.0.7 triggerer: 172.19.0.5 worker: 172.19.0.8
MYSQL (
SHOW ENGINE INNODB STATUS;
)Airflow env
Are you willing to submit PR?
Code of Conduct