[MDEV-16183] TokuDB tests fail on Fedora 28 Created: 2018-05-15  Updated: 2018-12-11  Resolved: 2018-05-17

Status: Closed
Project: MariaDB Server
Component/s: Packaging, Platform RedHat, Tests
Affects Version/s: 10.2
Fix Version/s: 10.2.15, 10.3.7

Type: Bug Priority: Blocker
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-17953 MariaDB 10.2.19 with TokuDB incompati... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-fedora28-amd64/builds/23/steps/mtr/logs/stdio

10.2 182db5a1b79e0be27e8191f9bea7c8cd3dbe22a3

tokudb_mariadb.xa-recovery-9214 'innodb' w2 [ fail ]
        Test ended at 2018-05-15 15:17:59
 
CURRENT_TEST: tokudb_mariadb.xa-recovery-9214
 
 
Failed to start mysqld.1
mysqltest failed but provided no output
 
 
 - skipping '/dev/shm/var/2/log/tokudb_mariadb.xa-recovery-9214-innodb/'
 
Retrying test tokudb_mariadb.xa-recovery-9214, attempt(2/3)...
 
worker[2] > Restart  - not started
***Warnings generated in error logs during shutdown after running tests: tokudb_mariadb.xa-recovery-9214
 
2018-05-15 15:17:57 139751156107520 [ERROR] Couldn't load plugins from 'ha_tokudb.so'.
2018-05-15 15:17:58 139751156107520 [ERROR] /usr/sbin/mysqld: unknown option '--tokudb'
2018-05-15 15:17:58 139751156107520 [ERROR] Aborting



 Comments   
Comment by Sergei Golubchik [ 2018-05-16 ]

The error is

2018-05-16  2:26:08 140039501175040 [ERROR] Can't open shared library '/usr/lib64/mysql/plugin/ha_tokudb.so' (errno: 2, /lib64/libjemalloc.so.2: cannot allocate memory in static TLS block)

This comes from the new jemalloc (see https://github.com/jemalloc/jemalloc/issues/937) when it's dlopen-ed or linked with a module that is dlopen-ed. Which is exactly our case, jemalloc is linked with tokudb, and tokudb is dlopen-ed.

Comment by Sergei Golubchik [ 2018-05-17 ]

The fix: don't link TokuDB with jemalloc on FC28. Instead, let's LD_PRELOAD jemalloc when TokuDB is installed.

Generated at Thu Feb 08 08:27:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.