Reindexing JIRA Results in Communications Link Failure During Commit

Related content

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When reindexing JIRA, the following exception appears in the log:

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:

  1. Increase the lock wait_timeouton MySQL server at the mysql prompt, for example:

    set global innodb_lock_wait_timeout = 300;

    The above query will increase the lock wait_timeout to 300 seconds.

  2. By using the MySQL Administrator tool, increase the Various - Lock Wait Timeout from Startup Variables >> InnoDB Parameters:

Last modified on Mar 21, 2024

Was this helpful?

Yes
No
Provide feedback about this article

Related content

Powered by Confluence and Scroll Viewport.