[MDEV-6770] Tokudb plugin won't load when upgrading from 10.0.13 to 10.0.14 Created: 2014-09-23  Updated: 2014-09-28  Resolved: 2014-09-28

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - TokuDB
Affects Version/s: 10.0.14
Fix Version/s: 10.0.14

Type: Bug Priority: Blocker
Reporter: Peter de Kraker Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: plugins, tokudb
Environment:

Ubuntu 12.04 64bit, Ubuntu 14.04 64bit


 Description   

Apt-get showed that there was a update for Mariadb 10.0.13. I updated on my staging server (Ubuntu 14.04), and although the update went ok, after the restart of Mariadb it wouldn't load Tokudb plugin anymore and all my Tokudb tables where shown as 'in use'.

I also tested this on a production server, with Ubuntu 12.04, and exact same results.

Seems to me that the tokudb plugin in 10.0.14 has a error, and I don't understand it is released.

After installing 10.0.13 again, everything works ok.

There is no error message at all with information. Transparant huge pages are disabled, diskspace is ok.

10.0.14 log:

140923 16:22:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
 
140923 16:22:36 [Note] InnoDB: Using mutexes to ref count buffer pool pages
 
140923 16:22:36 [Note] InnoDB: The InnoDB memory heap is disabled
 
140923 16:22:36 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
140923 16:22:36 [Note] InnoDB: Memory barrier is not used
 
140923 16:22:36 [Note] InnoDB: Compressed tables use zlib 1.2.8
 
140923 16:22:36 [Note] InnoDB: Using Linux native AIO
 
140923 16:22:36 [Note] InnoDB: Using CPU crc32 instructions
 
140923 16:22:36 [Note] InnoDB: Initializing buffer pool, size = 300.0M
 
140923 16:22:36 [Note] InnoDB: Completed initialization of buffer pool
 
140923 16:22:36 [Note] InnoDB: Highest supported file format is Barracuda.
 
140923 16:22:37 [Note] InnoDB: 128 rollback segment(s) are active.
 
140923 16:22:37 [Note] InnoDB: Waiting for purge to start
 
140923 16:22:37 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 19140858019
 
140923 16:22:37 [Note] Plugin 'FEEDBACK' is disabled.
 
140923 16:22:37 [ERROR] Function 'TokuDB' already exists
 
140923 16:22:37 [Warning] Couldn't load plugin named 'TokuDB' with soname 'ha_tokudb.so'.
 
140923 16:22:37 [ERROR] Plugin 'TokuDB' init function returned error.
 
140923 16:22:37 [ERROR] Plugin 'TokuDB' registration as a STORAGE ENGINE failed.
 
140923 16:22:37 [Note] Server socket created on IP: '0.0.0.0'.
 
140923 16:22:37 [Note] Event Scheduler: Loaded 0 events
 
140923 16:22:37 [Note] Reading of all Master_info entries succeded
 
140923 16:22:37 [Note] Added new Master_info '' to hash table
 
140923 16:22:37 [Note] /usr/sbin/mysqld: ready for connections.
 
Version: '10.0.14-MariaDB-1~trusty-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
 
140923 16:28:57 [Note] /usr/sbin/mysqld: Normal shutdown



 Comments   
Comment by Elena Stepanova [ 2014-09-23 ]

Thanks a lot for the heads up. The release has not become official yet, you caught it while packages were being synced to the mirrors.

For now, the packages are pulled from the repo. They will be re-uploaded later, and this issue will be updated when we know the best course of action after this unsuccessful upgrade.

How urgent is the problem for you, were you able to get your instance run again by downgrading to 10.0.13?

Sorry for the trouble.

Comment by Peter de Kraker [ 2014-09-23 ]

Hi,

Switching to a 10.0.13 repo and uninstalling mariadb* and reinstalling mariadb-server made it work again. No issues with the downgrade.

I don't know if the specifics of my installation are causing this tokudb plugin issue. I have no time to test it with a fresh install and upgrade. I did have perconadb installed before mariadb a few months ago, and had some issues at that time when I ran `install plugin` for TokuDb and switchting to MariaDB after that. It could be that somehow the version of TokuDB is manually locked in my MariaDB install and it therefor refuses to upgrade, but I don't know enough to investigate that. tokudb.cnf is default one of Mariadb with added memory settings.

Comment by Elena Stepanova [ 2014-09-23 ]

I don't know if the specifics of my installation are causing this tokudb plugin issue. I have no time to test it with a fresh install and upgrade.

It is okay, we were able to reproduce the problem and it is being fixed now. Thanks again for the prompt report.

Comment by Elena Stepanova [ 2014-09-28 ]

serg,
This report should probably be closed as fixed in 10.0.14 rather than moved to 10.0.15?

Comment by Peter de Kraker [ 2014-09-28 ]

Great to see it is fixed. I just tested the 10.0.0.14 release, and everything works ok. Only thing I don't really understand is why the release notes say tokudb is updated to 7.5 and the internal tokudb version code is still on 7.1.8. But that might be something for another issue.

Comment by Sergei Golubchik [ 2014-09-28 ]

Peterdk because 10.0.14 has TokuDB 7.5.0. That was the fix, 7.1.8 was unable to read to tables created by MariaDB 10.0.13 (because of a merge glitch in 10.0.13). But I've forgot to update TokuDB version number before the release. So MariaDB 10.0.14 has TokuDB 7.5.0, despite saying that it's 7.1.8.

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