MySQL Transaction of size exceeds specified limit. To increase the limit please adjust group_replication_transaction_size_limit option.
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 trying to perform a large bulk action or a major version upgrade of Jira, you may encounter this error.
Cause
MySQL has a limit configured on replicated transactions when it is used in a clustered configuration. This may only manifest when performing certain operations such as an upgrade from 8.x → 9.x versions, as there are a lot of upgrade tasks running against the database.
Solution
Use the system variable group_replication_transaction_size_limit to specify a maximum transaction size that the group accepts. In MySQL 8.0, this system variable defaults to a maximum transaction size of 150000000 bytes (approximately 143 MB). Transactions above this size are rolled back and are not sent to Group Replication's Group Communication System (GCS) for distribution to the group. Adjust the value of this variable depending on the maximum message size that you need the group to tolerate, bearing in mind that the time taken to process a transaction is proportional to its size.
For more information about these configuration changes, please see MySQL Documentation here: https://dev.mysql.com/doc/refman/8.0/en/group-replication-limitations.html
Was this helpful?