As 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.
We are actively reporting on this issue with the affected versions, workarounds and ways to prevent this from updating until the issue is resolved here: Known Issues Status Page
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.
Attachments
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/magento2
It's because Magento uses an awful IN clause with quotes around numbers when it does the indexing and MariaDB 10.3's optimizer doesn't efficiently convert to an integer. There's a workaround patch for the old Zend framework code they use.
MariaDB also aware of issue at [MDEV-20871] Queries with entity_id IN ('1', '2', ..... , '70000') run much slower in MariaDB 10.3.18 than on MariaDB 10.1 - Jira
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: 104.219.172.10
* cpanel-addons-production-feed: 104.219.172.10
* cpanel-plugins: 104.219.172.10
* 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
# 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: 104.219.172.10
* cpanel-addons-production-feed: 104.219.172.10
* cpanel-plugins: 104.219.172.10
* 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
MariaDB has released updates for all affected versions but they are still not available when we perform updates. Will it be available soon?
The packages are available I just installed 10.3.20 on a test environment.
Code:
[[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_64I'd suggest running
yum clean all and checking again.
| 1 2 | yum downgrade MariaDB-* -y whmapi1 update_updateconf RPMUP=manual UPDATES=manual |
This will downgrade MariaDB installation to the previous version
Line 2 will cancel automatic update on WHM/CPanel installations
If you are not using WHM, use line 1 only OR you can downgrade the repository individually too
| yum downgrade MariaDB-server MariaDB-common MariaDB-shared MariaDB-client MariaDB-compat MariaDB-devel |
Last edited by a moderator: