asd855280 opened a new issue, #25750:
URL: https://github.com/apache/airflow/issues/25750
### Apache Airflow version
Other Airflow 2 version
### What happened
We are seeing airflow DAG reported failed occasionally due to table lock
timeout while delete from xcom table
Exception:
(pymysql.err.OperationalError) (1205, 'Lock wait timeout exceeded; try
restarting transaction')
[SQL: DELETE FROM xcom WHERE xcom.dag_id = %(dag_id_1)s AND xcom.task_id =
%(task_id_1)s AND xcom.execution_date = %(execution_date_1)s]
[parameters: {'dag_id_1': 'XXXXXXX', 'task_id_1': 'XXXXXXXX',
'execution_date_1': datetime.datetime(2022, 8, 16, 0, 0)}]
### What you think should happen instead
Possibly extended period of table transaction before the deleting from xcom
cause the lock timeout exceeded issue
### How to reproduce
We have 6 instances running
Using celery worker mode
node1: metadata db(MySQL 8), message queue(redis 6), webserver, celery
flower and worker1
node2: worker2
node3: scheduler 1
node4: scheduler 2
node5: worker3
node6: worker4
basic configuration:
max_dagruns_to_create_per_loop = 32
max_dagruns_per_loop_to_schedule = 32
use_row_level_locking = true
worker_autoscale = 256,16
### Operating System
NAME="Rocky Linux" VERSION="8.6 (Green Obsidian)" ID="rocky" ID_LIKE="rhel
centos fedora" VERSION_ID="8.6" PLATFORM_ID="platform:el8" PRETTY_NAME="Rocky
Linux 8.6 (Green Obsidian)" ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:rocky:rocky:8:GA" HOME_URL="https://rockylinux.org/";
BUG_REPORT_URL="https://bugs.rockylinux.org/"; ROCKY_SUPPORT_PRODUCT="Rocky
Linux" ROCKY_SUPPORT_PRODUCT_VERSION="8" REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8"
### Versions of Apache Airflow Providers
airflow 2.1.0
### Deployment
Virtualenv installation
### Deployment details
_No response_
### 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]
