SOLVED [CPANEL-26469] [DOC-13607] Considering the upgrade from MySQL 5.7.28 to Maria 10.3 and I have a few questions

[rudtek]

I am running a VPS with CentOS and have many sub cPanel accounts. Most of them are running wordpress with databases using myisam storage engine. I first considering upgrading to InnoDB but ran into "strict" policy issues where my default date values were 00-00-0000 etc.

I thought It may be easier to update to mariaDB first but see that it has some of the same issues. Now I'm a bit concerned with moving forward and not being able to go back if it breaks all my (client) sites.

Can any kind person please help me figure out my steps?

do I need to upgrade all database tables to InnoDB first (and deal with "strict" issues) then move to Maria? Or do change to Maria First?

do I deal with strict issues at all or just ignore them?

If I do change to Maria and all the sites break...what then? Is there a way to back up every thing and revert or is there a solid process to identify breaking issues and fix them?

Sorry for the naivety here, and I appreciate all help!

 

[cPanelLauren]

Hello,

cPanel does not currently support the update from 5.7 to MariaDB 10.2 or 10.3 - please see our documentation here: MySQL or MariaDB Upgrade - Version 84 Documentation - cPanel Documentation

Specifically

• Do not upgrade from MySQL 5.7 to MariaDB 10.2 or 10.3. Those versions of MariaDB do not contain the sys schema, which will cause check table calls to fail. If you do accidentally upgrade from MySQL 5.7 to MariaDB 10.2 or 10.3, you must manually remove that schema from your databases.

 

[rudtek]

Hello,

cPanel does not currently support the update from 5.7 to MariaDB 10.2 or 10.3 - please see our documentation here: MySQL or MariaDB Upgrade - Version 84 Documentation - cPanel Documentation

Specifically

• Do not upgrade from MySQL 5.7 to MariaDB 10.2 or 10.3. Those versions of MariaDB do not contain the sys schema, which will cause check table calls to fail. If you do accidentally upgrade from MySQL 5.7 to MariaDB 10.2 or 10.3, you must manually remove that schema from your databases.

Thanks for the reply...
1.. Please see the two images I've uploaded. It seems that the upgrade IS supported. (area I circled in blue explicitly states this)
2. Do you have any suggestions or help with the process (or my other questions) that WILL work to upgrade or am I stuck where I am forever?

 

[GOT]

We've done a number of upgrades from 5.7 to 10.3. I do not think you need to convert any tables ahead of time. If you are worried or have issues with the strict setting, it can always be disabled via my.cnf.

 

[GOT]

I would not try to isntall 10.2. I'm not sure why that is showing as a viable option for you. It shouldn't and normally doesn't.

 

[cPanelLauren]

Hello,

You're right, there is some discrepancy between the documentation and the UI. I've opened DOC-13607 to have this looked further into. CPANEL-26469 was opened to automatically address issues with updating but this was not fixed in any versions lower than v86 as of right now, according to the case.

MariaDB's purpose is to be a drop-in replacement for MySQL, the issue with 10.2 and higher being the differences in the sys schema tables (they both use schemas like this but this specific one isn't recognized by MariaDB) - the point of concern for me is I don't believe those are the same issues noted in the warning in the MySQL update UI - which is part of what I'm attempting to suss out currently.

The issue presents itself in mysqldump - have any of the conversions you've done @GOT had issues with db backups?

 

[cPanelLauren]

Hello,

I just wanted to update this thread that this issue has been marked as resolved in v86 of cPanel. This is referenced in our changelogs here: Change Logs - Change Logs - cPanel Documentation