Percona not being supported is - sorry for my wording - stupid. Percona XtraDB clustering is a common enterprise deployment for MySQL databases. InnoDB MySQL databases should work flawlessly in a Percona XtraDB setup - just migrations into the cluster could come with issues due to foreign table settings.

Martin Poirier made a comment in https://jira.atlassian.com/browse/JRASERVER-42012 that he was using Percona for more than 5 years now for confluence and Jira and didn't detect any issues. This doesn't mean that Atlassian supports it. That said i think it would be nice that after 4 years this thread is open Atlassian starts supporting percona cluster db. (We have several percona clusters and run a separate mysql instance for Atlassian products)

This is still an issue, because topic was open for a long time I raised a support ticket. The answer in short: "At this point, MySQL derivatives like Percona and MariaDB are not currently supported, and it's unclear whether they will be supported in the future". Hope that answers your question. I would say "vote" and keep watching the release notes!

Is this still an issue or is percona support now?

I've attempted to move database from MySQL server to Percona MySQL but it's not going as planned. Database import fails with:

Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

Table affected is PLUGINDATA which contains two varchar columns (PLUGINKEY and FILENAME). Data stored there looks binary (even though I haven't done extensive investigation), and thus cannot be inserted. Percona recommends changing that to TEXT or BLOB but it's not helping as these fields are used as unique indexes. This is also cause of "problems with plugins" mentioned earlier.

I'm using confluence 5.7.4

We are about to upgrade from Confluence 5.6.6 to 5.8.x and are already running Percona Clusters for all of our hosted Atlassian products (JIRA, Stash, Confluence) with no issues so far. Percona is a corporate standard for clustered MySQL so moving off that would be very difficult for us. Is this a show-stopper for our upgrade?

Thanks Peter. That is helpful. I still would like to know some specific issues that were seen with Percona usage to see if we are affected by them. If I can confirm we are experiencing these, I will make the case to switch back to vanilla MySQL but for us Percona has always shown performance improvements.

Hi,

We have encountered a number of support cases where switching over from Percona to the regular MySQL implementation was the solution. These include problems with plugin installation, stability and performance and also in a few cases I've seen InnoDB table corruption on the Confluence database as a result. Although these issues may or may not pop up with different versions or based on different usage patterns, but this still does not mean that everything is OK under the hood.

There could be problems discovered or undiscovered that only hit in on upgrades/plugin upgrades or certain operations that you do not perform daily. Switching to a supported database when there's already a problem can be quite problematic when you try to immediately solve the issue for your users. The bottom line is that we do not yet test with these (Percona and MariaDB) flavors of MySQL. So although it will not necessarily cause a problem, we cannot guarantee it to work either and when facing a support issue, we will likely try to eliminate any possible main contributors (if the source of the problem is unknown), one of which is obviously checking if the environment is supported (Java version, hosting OS, installed plugins and obviously database type).

I've raised this feature request because although we do not yet test with Percona and MariaDB, these flavors are now widely used and we should consider moving to the direction of supporting those, but I also did raise a documentation request relating to it (https://jira.atlassian.com/browse/CONF-36474), making sure that we put this information on the public documentation as there have been quite a number of cases where using Percona did cause an issue and the earlier versions of the documentation only specified to use MySQL, based on which one could easily assume that any derivatives are also supported and tested.

I hope the above answers your questions.

Cheers,

Peter Koczan

I am also interested in issues encountered with Percona - I have have been running Percona with Confluence and JIRA on multiple instances (small and large) over several years successfully. The only issue I ever encountered was with the upgrade to from 5.6.6 to 5.7 https://jira.atlassian.com/browse/CONF-36430 and switching to a datasource connection fixed the problem. This issue does not seem to be related specifically to Percona but rather the jdbc implementation: https://jira.atlassian.com/browse/CONF-36484

Also I know this may be outdated from 2012 but look at @Denise Unterwurzacher [Atlassian] 's response: https://answers.atlassian.com/questions/92504/is-percona-mysql-supported-for-confluence-jira

Hello,

What issues have been encountered with running Confluence on Percona? We are considering moving our Confluence instance to a Percona system.

Thanks!