Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
22.08.11
-
None
-
Using rocky linux 8.8, mariadb-galera version 10.11.6.
Here's partial output of lshw:
description: Computer
width: 64 bits
capabilities: smp vsyscall32
*-core
description: Motherboard
physical id: 0
*-memory
description: System memory
physical id: 0
size: 12GiB
*-cpu:0
product: AMD EPYC Processor (with IBPB)
vendor: Advanced Micro Devices [AMD]
physical id: 1
bus info: cpu@0
version: 23.1.2
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt x86-64 rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 arat
configuration: microcode=16777317
Using rocky linux 8.8, mariadb-galera version 10.11.6. Here's partial output of lshw: description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 12GiB *-cpu:0 product: AMD EPYC Processor (with IBPB) vendor: Advanced Micro Devices [AMD] physical id: 1 bus info: cpu@0 version: 23.1.2 width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt x86-64 rep_good nopl cpuid extd_apicid tsc_known_freq pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 arat configuration: microcode=16777317
-
MXS-SPRINT-206
Description
We have been using mariaDB on a project for a number of years. We are now moving to the galera cluster and using maxscale/cdc-client to get notifications of updates. One of our tables is defined as follows:
show create table nf_profile_json;
|
+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| Table | Create Table |
|
+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| nf_profile_json | CREATE TABLE `nf_profile_json` (
|
`nfinstanceid` binary(16) NOT NULL,
|
`nfprofile` longtext NOT NULL,
|
PRIMARY KEY (`nfinstanceid`) USING HASH
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_unicode_ci |
|
+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
1 row in set (0.000 sec)
|
If I insert a new entry in this table with a "small" key, it works fine. For example:
insert into nf_profile_json values (X'111111, "Some string");
|
This works fine. I see cdc-client gets triggered. However, if I use a true key value, such as:
insert into nf_profile_json values (X'11112222333344445555666677778888, "Some string");
|
This fails, I get an error in the maxscale log file:
2024-04-03 19:34:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1603714, record number 2.
|
2024-04-03 19:34:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1609339, record number 2.
|
2024-04-03 19:44:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1614292, record number 2.
|
2024-04-03 19:44:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1619917, record number 2.
|
2024-04-03 19:54:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1624870, record number 2.
|
2024-04-03 19:54:15 error : Failed to read field value 'nfinstanceid', type 'unknown type' at file offset 1630495, record number 2.
|
This is just a small portion of the log fine. I have not verified where the "breaking point" is where the key starts becoming too long.