Add support for MySQL 5.7

Brian Kramer shared this idea 1 year ago
Open Discussion

This is a duplicate request of: https://features.cpanel.net/topic/add-support-for-mysql-57#comment-47215

That request was archived long ago as it was made prior to GA release. I do not know how to make an old request current and remove from the archive, and am not even sure there is an option to do so. "All feature requests" CPanel page does not show this request and I am not sure if it is being ignored due to the archive state.

Best Answer
photo

Okay, you've convinced us! This is back under consideration, and we want to see this added as well. We're already fully committed to what work will be completed in the first quarter of 2017, but when we go into planning for the second quarter this will be on the list of things to discuss. Thank you so much for your continued input, and I'll let you know as soon as there's any more information.

https://forums.cpanel.net/threads/discussion-of-mysql-5-7-support.592591/#post-2424635

Comments (65)

photo
1

As of this writing (2014-02-12), MySQL 5.7.x is within a "Milestone Release" state. This is a very volatile development stage and not production ready release cycle. As per Oracle's own warning with every milestone release:

"This is a milestone release, for use at your own risk. Significant development changes take place in milestone releases and you may encounter compatibility issues, such as data format changes that require attention in addition to the usual procedure of running mysql_upgrade. For example, you may find it necessary to dump your data with mysqldump before the upgrade and reload it afterward."

As per usual, we will be waiting until MySQL 5.7 reaches the "General Availability" state in which Oracle considers it to be production ready. At that time, MySQL 5.7 will be evaluated and considered for inclusion into cPanel & WHM.

photo
3

MySQL 5.7 reached the "General Availability" state :-)

photo
3

here's the proof. i need this version to implement replication multi master to master, please.

ac14f6b9aa44135861f249933893d968

photo
1

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

photo
2

I have been waiting over a year for this, any thoughts on timeline to add into CPanel?

photo
2

I would expect that once MySQL 5.7 hit GA status work had begun to provide it with cPanel (or would have already started once the releases hit the more stable phases) and that this feature request is not necessary. Please tell me i am right?

photo
2

Seeing that 5.5 will hit EOL the end of this year, 5.7 should be supported by then. I do not see why this even needs votes. It just needs to happen ASAP.

To continue being a competitive product WHM/CP needs support for PHP 7, MySQL 5.7, and MariaDB 10.1.

photo
1

+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?

photo
1

This however should be optional.

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

photo
1

Any news on that feature ?

photo
1

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.

photo
1

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

photo
1

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

photo
1

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

photo
1

Its more a cpanel issue, please contact them to add weight to the request:

http://cpanel.com/support/

This is the reply I got from cpanel:

Hello Simon,

Currently we don't have any updated information of the upgrade to MySQL 5.7 or PHP 7 within cPanel & WHM. This will be announced in our website when these updates are available. There are feature requests which have been published here:

https://features.cpanel.net/topic/add-support-for-mysql-57

and

https://features.cpanel.net/topic/php7-support

You could vote for them and add comments. Product Managers and Developers do watch these features to help set priorities for the release of new features.

Hope this helps

photo
1

Hi, forcing us to use mariadb is a problem because some web applications don't support Mariadb yet.

Some web applications show an error 500 while using mariadb. For now it is a good fix for us to use MySql because we don't need to modify scripts that are maintained by other companies.

I hope you will not force an update to Mariadb.

So for instance, The Booked web application does not like Mariadb. Only because of Booked, i must use mysql 5.6 now.

I am sure there are other web applications that don't support Mariadb yet.

photo
1

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

photo
3

Hi,

We really really need MySQL 5.7 support. We're using it as a standard for many many services on several platforms and don't plan to switch anytime soon :(

photo
1

Why not ? Have you noticed any compatibilty issues ?

photo
3

PS: I looked further into mariadb, my conclusions:

There are differences between MySQL and MariaDB, some large, some subtle > if it breaks something what can I say to my customers? Who will pay for all the debugging and troubleshooting if it goes wrong?

With MariaDB 10.1 differences are even bigger, they use now XtraDB by default: https://mariadb.com/kb/en/mariadb/xtradb-and-innodb/

In the end they might even grow further apart and nobody knows for sure who will win or what might or might not be compatible. Who know's MariaDB doesn't even exist anymore in 5 years while MySQL has been around since 1995 !

It's like the "battle" between Debian/Ubuntu etc. We like Debian because it's very stable and safe to use, others like Ubuntu because it's more progressive.

So in the end the choice should be up to the server owner and not enforced by cPanel!

photo
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.

photo
1

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 :)

photo
1

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.

photo
2

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.

photo
1

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.

photo
1

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.

photo
2

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

photo
1

I would like to add that as the move to php7 is also underway (massive performance improvements apparently) I am cautious about changing the database at the same time, and would be far happier staying with mysql updates for at least 6 months

photo
1

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

photo
1

I really need a tad bit of clarification here please. as stated by the team initially they have NO PLANS to implement MySQL 5.7 - is that EVER? or unless there is significant requests from the community?

also, as marina 10.1 and MySQL 5.6 further separate, and compatibility with migration seems daunting more and more daily...

IF the cPanel team is no longer wanting to support MySQL, then for me it begs that we upgrade NOW!!!

however, my question is... in cPanel your system states that the END OF LIFE for MySQL 5.6 is (February 28, 2018)... so, does that mean that if you do not choose to implement MySQL 5.7 that as of February 28, 2018 - updates stop and security then become a huge issue?

I am one that is thinking that if I do not upgrade NOW, I will be hosed in 2018... very near future!

I await the community and cPanel temas professional opinion on this question...

photo
1

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!

photo
1

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

photo
1

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.

photo
1

We're running MySQL 5.7 on other systems without cPanel with great success. Still can't believe this won't be supported :(

photo
1

Not supporting mysql 5.7 will exclude the ability to use percona to run external mysql servers.

photo
1

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

photo
1

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.

photo
1

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.

photo
1

It's all ridiculous like I said before :(

I hope support for 5.7 comes and soon!

photo
2

I'm amazed with MariaDB 10.0 performance, but although I know the few, small, incompatibilities with MySQL 5.6, the alleged "bugs" frequently comes out to be guilt of script developers who have procrastinated too much the use of MySQL good practices.

In example: WordPress and Joomla works great with MariaDB, but other less popular scripts, yet being very good pieces of software, specially those dedicated to email marketing (ArpReach, Mautic, Sendy) will have troubles when running under MariaDB. And that's a shame.

I'm very happy to migrate to MariaDB but unfortunately needed to keep a couple servers working with MySQL 5.6 to avoid compatibility issues with some scenarios.

photo
1

A lot of CMS vendors do not test against MariaDB, they only certify against MySQL. This can create pain points going forward as MySQL 5.7 becomes the standard over .6. I think the amount of votes to the positive vs negative shows how the community feels about this. At the very least cPanel should certify to 'remote management' of a MySQL 5.7 server so there are options. I know there is at least 1 really popular e-commerce application that has issues with MariaDB, or really anything that isn't MySQL. 5.6 works for now, but I have been receiving requests for 5.7 multiple times a week. Right now I have to recommend if these clients want 5.7, they need to forego cPanel.

photo
1

Thanks for your continued feedback here! We're definitely listening, though we haven't yet changed our direction. If/when that changes I'll definitely let everyone know.

photo
1

I just discovered two more popular commercial scripts that are only going to support MySQL 5.7 and have issues with MariaDB with their next release. There seems to be a big push in commerical scripts to push everyone to PHP7, which is great, but at the same time, they are also pushing to MySQL. I have yet to see a commerical php script that recommends MariaDB. Someone correct me if I am wrong?

photo
1

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.

photo
1

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.

photo
1

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

photo
1

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.

photo
3

Okay, you've convinced us! This is back under consideration, and we want to see this added as well. We're already fully committed to what work will be completed in the first quarter of 2017, but when we go into planning for the second quarter this will be on the list of things to discuss. Thank you so much for your continued input, and I'll let you know as soon as there's any more information.

https://forums.cpanel.net/threads/discussion-of-mysql-5-7-support.592591/#post-2424635

photo
2

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

Thanks a lot for sharing some more insight!

photo
1

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

photo
2

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 ;-)

photo
1

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.

photo
1

Maybe if we can continue the list of scripts that will require MySQL 5.7, we can help fast track this. As the industry push to PHP7 seems to get stronger and stronger. I got word with SupportPal who is a popular help desk solution, especially in the hosting community as it integrates very well with WHMCS. That as they continue development, and move from their latest beta release which uses PHP7, they will only support MySQL and specifically 5.7. They arent saying it wont work with MariaDB, but they will provide zero support on database issues if you are running MariaDB

While I plan on personally running a test in VMs, there are reports that PHP7 with MySQL 5.7 is faster and lower resources then PHP 7 and MariaDB 10.x. While we all are striving for the best performance for our clients, I think a decision being made on this sooner then later is the best for the community.

photo
1

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.

photo
1

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.

photo
3

I'm in a situation where I can't use an app I just bought because I can't get a cpanel with mysql 5.7. It's an awesome app and this is killing me. I love cpanel, but we really need you guys to embrace the future and push with us to create a better web experience for our clients. Change is constant and we need you to help us create that rate.

photo
1

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!

photo
1

It appears that Joomla is the next major script that will be requiring MySQL 5.7. Their stance has always been, while we work with MariaDB and the forks, our development is in MySQL. Since there is incompatibilities with MariaDB and 5.7, it appears as they go forward they will leave MariaDB support behind.

Hope the movement on this happens sooner then later as at this point we are about ready to start up our next shared hosting servers and it looks like we are going to be forced to do so on DirectAdmin just so we can have 5.7 support for our paying clients.

photo
1

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

photo
1

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!

photo
1

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?

photo
1

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.

photo
1

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.

photo
1

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

photo
1

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".