Reindexing JIRA Results in Communications Link Failure During Commit
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When reindexing JIRA, the following exception appears in the log:
1
2010-09-01 09:55:08,954 JiraTaskExectionThread-1 WARN admin 35560x41x1 17x0nj8 /secure/admin/jira/IndexReIndex.jspa [NoModule\] [SQLProcessor.commit\]: SQL Exception occurred on commit. Error was:com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Communications link failure during commit(). Transaction resolution unknown.
Cause
The innodb_lock_wait_timeout on MySQL server is too short. It seems that there is a SQL process sleeping for the entire indexing process which exceeds the innodb_lock_wait_timeout value.
Resolution
There are 2 solutions to this problem:
Increase the lock
wait_timeouton MySQL server at the mysql prompt, for example:1set global innodb_lock_wait_timeout = 300;The above query will increase the lock wait_timeout to 300 seconds.
By using the MySQL Administrator tool, increase the
Various - Lock Wait TimeoutfromStartup Variables >> InnoDB Parameters:
Was this helpful?