Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The hard-coded VARCHAR length limit (2048) is not enough to store all variables in wsrep_provider_options, resulting in truncation and warnings.
This bug is deemed low severity by upstream: https://jira.mariadb.org/browse/MDEV-24267
There is no known workaround, but the log messages can be ignored or filtered out in case the application being served by the database can handle the truncation.
Version-Release number of selected component (if applicable):
mariadb-server.x86_64 3:10.3.28-1.module+el8.3.0+10472+7adc332a
How reproducible:
Always.
Steps to Reproduce:
1. Set up a MariaDB Galera cluster.
2. MariaDB [db]> SHOW VARIABLES LIKE 'wsrep_provider_options' \G
3. Notice that data has been truncated.
Actual results:
The data has been truncated. The JDBC driver for example also logs this:
Mar 23 11:34:54 secure5 ciphermail-gateway-backend[1334105]: 23 Mar 2022 11:34:54 | WARN SQL Warning: 1265, SQLState: 01000 (org.hibernate.util.JDBCExceptionReporter) [defaultEventExecutorGroup-4-3]
Mar 23 11:34:54 secure5 ciphermail-gateway-backend[1334105]: 23 Mar 2022 11:34:54 | WARN Data truncated for column 'VARIABLE_VALUE' at row 628 (org.hibernate.util.JDBCExceptionReporter) [defaultEventExecutorGroup-4-3]
Expected results:
The column should be large enough to store the wsrep_provider_options data.
Hi,
I think the upstream responded in the upstream JIRA ticker that it is not actually a bug, bug an expected warning message that can be safely ignored.
is there anything I can do for you, or can I close this BZ ticket as 'NOT a BUG' ?
Hi Michal, feel free to close this issue. As I comment in the upstream bug thread, this doesn't seem to be an issue in the software itself, but more of a documentation thing.