As a sidenote Magento 2.3 has indexing issues with 10.3 which can cause crons to run for hours using high resources.This has been nasty. Any server running Magento v2 has been crashing for me. It uses a lot of FTS and FK.
Affects MariaDB 10.1 to 10.3 too.
Yes, you can. I was able to without any issues. My MariaDB was showing non-active and would not activate/run. You may need to restart the server or SQL Server after doing the downgrade. Mine was up and running with no restart but I restarted it anyway as the "Status" of MarianDB was still showing "down". This has not resolved the status shows "down" tho. Even tho it is up and running now and the sites are connecting to the database once again.Can you downgrade if mariadb is already down?
Going a bit off-topic but it looks like the indexing issue is being looked at. Catalog Category Indexing takes very long on MariaDB 10.3 with many products · Issue #25199 · magento/magento2As a sidenote Magento 2.3 has indexing issues with 10.3 which can cause crons to run for hours using high resources.
This, in conjunction with the Magento 2.3 layered navigation bug (when using mysql catalog search) crashes the servers. We migrated Magento back to 10.1 servers to resolve indexing issues and used Elasticsearch to avoid the search bug.
I seem to be unable to downgrade. I get the following output. Any suggestions?
# yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel
Loaded plugins: fastestmirror, universal-hooks
Setting up Downgrade Process
Loading mirror speeds from cached hostfile
* EA4: 184.108.40.206
* cpanel-addons-production-feed: 220.127.116.11
* cpanel-plugins: 18.104.22.168
* base: mirror.arizona.edu
* extras: mirror.arizona.edu
* updates: mirror.arizona.edu
EA4 | 2.9 kB 00:00 ...
cpanel-addons-production-feed | 2.9 kB 00:00 ...
cpanel-plugins | 2.9 kB 00:00 ...
MariaDB102 | 2.9 kB 00:00
base | 3.7 kB 00:00
extras | 3.4 kB 00:00
updates | 3.4 kB 00:00
Nothing to do
rpm -qa |grep MariaDB
The packages are available I just installed 10.3.20 on a test environment.MariaDB has released updates for all affected versions but they are still not available when we perform updates. Will it be available soon?
[[email protected] ~]# rpm -qa |grep Maria MariaDB-common-10.3.20-1.el7.centos.x86_64 MariaDB-devel-10.3.20-1.el7.centos.x86_64 MariaDB-shared-10.3.20-1.el7.centos.x86_64 MariaDB-client-10.3.20-1.el7.centos.x86_64 MariaDB-server-10.3.20-1.el7.centos.x86_64 MariaDB-compat-10.3.20-1.el7.centos.x86_64
yum clean alland checking again.
|yum downgrade MariaDB-* -y|
whmapi1 update_updateconf RPMUP=manual UPDATES=manual
|yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel|
|Thread starter||Similar threads||Forum||Replies||Date|
|2||During updating from mysql 5.6 to MariaDB 10.3 I got these errors...||Databases||3|
|S||SOLVED MariaDB 10.3.26 causing adminbin error (MySQL currently offline) When it's not!||Databases||11|
|S||Question about MariaDB Update (I have an error)||Databases||1|
|M||systemctl start mariadb error but systemctl status mysql running||Databases||1|
|G||cpanel update error after change to MariaDB||Databases||6|
|During updating from mysql 5.6 to MariaDB 10.3 I got these errors...|
|SOLVED MariaDB 10.3.26 causing adminbin error (MySQL currently offline) When it's not!|
|Question about MariaDB Update (I have an error)|
|systemctl start mariadb error but systemctl status mysql running|
|cpanel update error after change to MariaDB|