RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

An update for MariaDB 10.3 in RHEL 8 is planned.

This update is expected to be a rebase to the latest possible upstream version, with aditional fixes.
That means this update will cover a number of CVEs fixed by upstream.

---

We also plan to update MariaDB 10.3 in RHSCL to sync versions between RHSCL and RHEL 8 to ease the upgrade from RHEL 7 to RHEL 8.

---

This is a tracker bug.
It should have set "DEPENDS ON:" against all other Bugzilla tickets which will be part of the update.

Hi,
@Michael Schorm,

Please consider rebasing to 10.3.28.
Version 10.3.27 suffers from a critical MariaDB bug that causes crashes during long write operations. I noticed this when loading a 100GB dump file. MariaDB would crash around 60-70 GB mark. The workaround for me was to downgrade back to 10.3.17. It did solve the issue, but this old version suffers from other bugs.

Its reported to be fixed in 10.3.28:
https://jira.mariadb.org/browse/MDEV-24275
And in 10.3.28 release notes: https://mariadb.com/kb/en/mariadb-10328-release-notes/
It says "MDEV-24275 - InnoDB persistent stats analyze forces full scan forcing lock crash"