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

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

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.