Preventing transaction issue when resuming a Job Conductor trigger with a MySQL database

EnrichVersion
6.4
6.3
6.2
6.1
6.0
5.6
EnrichProdName
Talend Big Data
Talend Data Integration
Talend Real-Time Big Data Platform
Talend ESB
Talend Data Services Platform
Talend MDM Platform
Talend Data Fabric
Talend Big Data Platform
Talend Data Management Platform
task
Deployment > Scheduling > Scheduling Jobs
Data Quality and Preparation > Third-party systems > Database components > MySQL components
Data Governance > Third-party systems > Database components > MySQL components
Design and Development > Third-party systems > Database components > MySQL components
EnrichPlatform
Talend JobServer
Talend Administration Center

Preventing transaction issue when resuming a Job Conductor trigger with a MySQL database

When resuming a trigger on the Job Conductor page of Talend Administration Center, MySQL users may get the following error: Lock wait timeout exceeded; try restarting transaction

To solve this issue, you need to edit a MySQL configuration file.

Procedure

  1. Open the following configuration file: mysql.ini or mysql.cnf
  2. Edit it as follows and save your changes:
    mysqld]
    transaction-isolation=READ-COMMITTED

    This transaction isolation level will solve the issue at next server start-up.

    For more information on isolation levels, read this section of the MySQL documentation.