[midPoint] v3.8 and MariaDB 10.3.x?

[Wojciech Staszewski]

OK, got it.

I adjusted the innodb page size to match the ssd raid block size: 4KB,
and this lowered the key size proportionally to 768 bytes.
After restoring default 16KB page size everything is ok.

Regards!
WS


W dniu 15.07.2018 o 15:34, Wojciech Staszewski pisze:
> Hello!
>
> Is MariaDB v 10.3.x supported by midPoint 3.8?
>
> I have a problem importing empty database structure in freshly
> intalled environment:
>
> # mysql -p midpoint < mysql-3.8-all.sql
> Enter password:
> ERROR 1071 (42000) at line 178: Specified key was too long; max key
> length is 768 bytes
>
> The MariaDB documentation says, that:
>
>
>         |innodb_default_row_format = dynamic (default),
>         innodb_large_prefix - removed in 10.3.1
>         innodb_file_format = |||Barracuda (default)||
>
> So the max key length should be 3072 bytes by default.
>
> System spec: CentOS 7 64bit, MariaDB 10.3.8
> Hardware: 2 x Intel(R) Xeon(R) Gold 5120 CPU @ 2.20GHz (56 cores+ht
> total), 256GB RAM, Hardware RAID 10 of 8xSSD for database, separate HW
> raid for system.
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20180715/780ea0f8/attachment.htm>