Add support for MySQL 5.7

Upgrade to MariaDB 10.1. It can do multi-master replication.

+1

Would be great if cPanel could keep the "Best Answer" of such important feature requests up to date with their latest progress so everybody can instantly see what is going on. Maybe add a link to a central place where all progress of the upcoming release can be put?

This however should be optional.

We host many projects with older code which do not work with the newest releases of MySQL / PHP.

Unfortunately we currently are not planning for this request to be completed, as we're moving toward full support of MariaDB, and away from MySQL. Please continue to add your vote to the request, however, if you are interested in us supporting MySQL 5.7.

wrong decision, for us who have gis needs and the performance or mysql5.7 coupled with php7

Away from MySQL ? Will my existing DB work with MariaDB ?

Yup! There would be no necessary work from you for the upgrade, and our upgrade process will get you completely upgraded to MariaDB automatically. You can read more about that here: https://documentation.cpanel.net/pages/viewpage.action?pageId=1507908

Which version of mariadb have you tested it on ? We have had no issues migrating from mysql 5.1 to mariadb 10.1

For xtraDB I belive that it's fully backwards compatible, just better optimised for modern hardwarehttps://mariadb.com/kb/en/mariadb/about-xtradb/

1. It is fully backwards compatible, and it identifies itself to MariaDB as "ENGINE=InnoDB" (just like InnoDB), and so can be used as a drop-in replacement for standard InnoDB.

When we moved 400+ databases from MySQL 5.1 to Mariadb 10.1, only one database had an issue, it was using 1700 columns whereas Aria seems to limit the number of columns to 1000 just like innodb does.

There was obviously a design error in that database structure and it's quite a rare issue.

Hi Monarobase,

I perfectly believe you, but I heard stories like that before. Or even ourselves had no issues, while others had tons of issues :(

It probably depends on what you're using. If you have only one CMS or application that has issues, but you run 100's of them, the issues and costs quickly go up!

Even if it's completely true, that also doesn't provide a solution to my other arguments :)

If you increase MySQL version it can also break applications so I don't belive you take a bigger risk moving from mysql 5.5 to 5.7 than from 5.5 to mariadb 10.1

If you use a Mariadb specific feature than you might not be able to move from mariadb to mysql but the opposite should never cause any problems.

MariaDB's approach so far has been to add new features but remain compatible with previous ones.

MariaDB is replacing MySQL in more and more servers (Most Redhat, CentOS users, lots of Debian/Ubuntu users…) so more an more scripts will be testing against mariadb as well as oracle mysql.

The way I see it, MySQL stopped being true MySQL when Oracle purchased it. It then split in two to become Oracle MySQL vs Mariadb/Percona

Mariadb is maintained by the original MySQL developpers and all MySQL kept was the name.

Sorry, I cannot agree. First example I look into is Magento. While it should work, there is no official support. I even read threads of people running into issues.

It's also about support. If the app does not officially support it, then there it stops! No serious enterprise will ever run something on a non supported database. If it goes wrong, it's also easy for the other party to tell: Sorry, no support from us. Database is not supported. I have had issues like this.

My conclusion: we need to be free of choice. Period. We should not be enforced.

If php version is 5.6 then mysql version should be 5.7 atleast. many open software like magento laravel dont support old mysql version now.

THIS^^ - If php version is 5.6 then mysql version should be 5.7 at least. many open software like magento laravel dont support old mysql version now.

Megento is compatible with MariaDB, Laravel ships by default with Mariadb on homestead.

MySQL 5.6 is available, and will be maintained for alot more than the 6 months you require :)

No problem at all! To clarify: We currently do not have any plans to implement MySQL 5.7. The nature of life, however, has lead us away from using definitives. Since it continues to come up, however, we do continue to discuss it internally. If our plan changes at all I'll make sure everyone here know!

Mysql upgrade goes through all versions so in 2018 you will go through all versions, that would ne mysql 5.6 to mariadb 10.0 to mariadb 10.1 etc. So you can wait until it's end of life then to keep it secure you will have to upgrade to mariadb.P

To me, it sounds like the plan for MySQL 5.7 is never, but from a fellow developers perspective, I wouldn't want to wait until 2018 to upgrade since the speed boosts from either MySQL 5.7 or MariaDB 10 are ridiculously better, regardless which way you go. Plus by then, the next upgrade for both will most likely be coming around the corner. So the real question you have to ask yourself is MariaDB 10 or no more Cpanel... or at least that is the question that me and my fellow coworkers are asking ourselves.

That is potentially true, if Percona has the same mysql system table changes as MySQL 5.7.

As external MySQLs servers are becoming more and more common with clusters, I feel this is a big mistake not to support 5.7. Also as MariaDB and MySQL drift apart in feature set, this will highly limit future applications from running on cPanel that coded to use the MySQL feature sets.

No, it fails on the simple fact that Percona reports as regular mysql 5.7.

On a side note; Percona aims to be a drop-in binary replacement for the original mysql binary, so they tend to stay true to the APIs set by official MySQL.

It's all ridiculous like I said before :(

I hope support for 5.7 comes and soon!

We're running MariaDB 10.1 with 600 users and none of them have found an incompatible script so far.

What scripts have you found that won't work with mariadb ?

The only case we came accross was with some of the first versions of Magento 2 whicih required MySQL 5.7 and didn't allow 10.1 for Mariadb as an acceptable value. Their users quickly requested MariaDB support and it was added soon after this.

I'm intererested to have some incompatible scripts to test.

Sunshop is our major one that the next version is going to be incompatible with MariaDB. While this does not have the popularity of Magento as Magento is free. This is a highly used commercial script and over the years we have worked with many of their clients. In saying that, the next major version is still months away, but they have already stated they will not support MariaDB and will force PHP7 and MySQL 5.7.

The other one that I know if is Cubescripts which is a real estate script. They as well have said they are going to require PHP7 and MySQL 5.7 and not support MariaDB.

Yes these are both paid solutions, but we are seeing more and more paid scripts force to PHP7 and as they do, it appears that some are starting to require MySQL 5.7.

So basically cPanel is telling us, the customers that are typically amazing customer because they are serious about the scripts they use on their websites, we are no longer going to be able to support.

As far as Linux goes, we have always been a cPanel house internally. We do offer DirectAdmin for a few client that want to save some money, but our primary push is cPanel.

Looks like that might change in coming months as we will be forced to go to Plesk, DirectAdmin, or Interworx all who fully support MySQL 5.7 in some form or fashion.

I have been very impressed with cPanel as of lately compared to years past, but this abandonment of MySQL 5.7 in turn, which creates abandoment of paid php scripts is starting to become worrysome.

Hello everybody. I can tell about these three email mailing/marketing scripts being incompatible with MariaDB 10:

- Sendy (premium)

- Arpreach (premium)

- Mautic (open source)

It was pretty difficult for me to discover why these apps weren't working. But in the end, the issue was the same: looks like in MariaDB you cannot insert a null value in a field IF the default value of that field wasn't previously defined as null in the db structure. It's a common mistake any developer may incur when working solo with lots of tables/fields. Indeed, you can fix it by simply alter the default values of the fields in a currently installed database. Nothing that a small script couldn't fix. Such a fix works well with MySQL 5.x because it is part of the good practices they recommend. It only happens that MariaDB is more strict when it comes to follow rules: they enforce it.

I know Sendy and Mautic authors will try to dive into it but there is no ETA for a fix since they don't use MariaDB for development, hence have not unit tests for this engine. In the other hand, the guys from Arpreach specifically told me they won't be willing to support MariaDB, ever.

So, here we decided we need to keep some servers with MySQL 5.6 and others with MariaDB 10. And frankly, now that cPanel released PHP 7 with PHP-FPM, I'm not seeing MariaDB performing any better than MySQL at all. And if you set MySQL to use RAM based cache and scripts supporting opcache or APCu, you couldn't tell what script is running over MySQL or MariaDB.

Then, for compatibility reasons, I will second this feature request: MySQL 5.7 is a necessary evil, in the same way PHP 5.3 still is for some scenarios. And using cPanel with LTS updates is not a good solution when the script developers are dropping 5.6 support in favor of 5.7.

Best regards

I've seen issues with Magento 1.x and MariaDB as well. Further, the incompatibilities with Magento 2 and MariaDB are a bit deeper than that stupid version check from what I recall. Magento does not now ( nor do they ever intend to) support MariaDB. This means if you run into an issue with it, you're on your own. Considering it's still the number 1 e-commerce software, it might be a good idea to roll out support for it.

Any update on this when this would be implemented? Getting more and more 5.7 requests :(

Thanks a lot for sharing some more insight!

No change yet, but keep the votes and use-cases coming!

Hi Benny, thanks for your reply. You guys know that MySQL 5.7 was released back in April 2013 already right? Don't really understand the arguments against this no-brainer ;-)

Certainly! Release dates aside, including MySQL 5.7 wasn't being considered until two months ago. I'll definitely let everyone know once there's any internal movement.

For the performance difference, check these benchmarks out :

https://mariadb.org/maria-10-1-mysql-5-7-commodity-hardware/

https://www.softizy.com/blog/mariadb-10-1-mysql-5-7-performances-ibm-power-8/

I don't think we can say MariaDB is slower than MySQL.

Those benchmarks were against the Databases alone. I was speaking of accessing through PHP7. Which will require setting up some VMs and doing some internal testing which I have not had time to do.

Partially, as cPanel decides to drag their feet on this one, we have to do our own internal planning and testing of how we move forward for clients that will have to use MySQL 5.7. Luckily we have only had a couple so far and their websites were large enough and had enough traffic we were able to transition them to Semi-Deds (VPS) with DirectAdmin. Just processed an order this morning of that exact case. In reality all that hurts is cPanel, as while we might not be ready to move all our shared servers to MySQL 5.7, this case would have been another VPS license sale for cPanel and not DirectAdmin.

Hey Joshua! Thanks so much for that, and welcome to the feature request site. Would you mind sharing which app it is that you're trying to use and can't? We definitely want to hear about it!

We host alot of Joomla websites on MariaDB 10.1 without any issues. Even some old versions.

Hi,

We know you don't need it, but tons of other people do. Even only for official support to have no issues when opening a ticket with certain vendors ... I hope you understand!

While this is currently true, as Joomla advances they are fixing issues with MySQL 5.7 but not addressing MariaDB at all.

There are plenty of reports of the Joomla 3.7 alpha release having issues with MariaDB. So as your clients upgrade their scripts for better functionality and security, what is your answer going to be to them?

I'm not saying I'm against cPanel supporting MySQL 5.7. There have been some scripts that are listed here as not compatible so it's a good idea. Was just saying that Joomla is not one of them.

Hey folks! Let's take this conversation to the forums or to a private email thread, to prevent all of the folks who are subscribed to see when this gets implemented from getting spammed by the debate.

Benny, be happy to take it the forums, can you point us to an appropriate thread to do so in? It was my understanding we moved all conversation here on feature requests so that it could stay out of the forums and be better tracked

We track votes and use-cases here on the request site, but discussing customer interactions and/or performance metrics of MySQL/MariaDB should likely be taken to a thread in "General Discussion" or perhaps in "Databases".