maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #02955
Error when migrating from TokuDB 7.5.2 to MariaDB 5.5.44 (works with 5.5.41)
I'm trying to migrate a TokuDB 7.5.2 server to MariaDB 5.5.44.
Since I can't stop the production server, I got a snapshot of the running
instance. So MariaDB will have to recover.
Unfortunately i get an error when TokuDB recovery is running in version
5.5.44.
Previously I tried with MariaDB 5.5.41 which worked fine. But since I'm
upgrading, I would like to use the latest version.
Mon Sep 28 03:53:37 2015 TokuFT recovery bw_begin_checkpoint at
158147092471 timestamp 1443133470008593 (bw_between)
Mon Sep 28 03:53:37 2015 TokuFT recovery turning around at begin checkpoint
158147092471 time 181293960
Mon Sep 28 03:53:37 2015 TokuFT recovery starts scanning forward to
158147993496 from 158147092471 left 901025 (fw_between)
/home/buildbot/buildbot/build/mariadb-5.5.44/storage/tokudb/ft-index/ft/serialize/ft-serialize.cc:275
deserialize_ft_versioned: Assertion `readsz >= translation_size_on_disk'
failed (errno=2)
: No such file or directory
Backtrace: (Note: toku_do_assert=0x0x7f769b49cf30)
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z19db_env_do_backtraceP8_IO_FILE+0x1b)[0x7f769b4996fb]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x80823)[0x7f769b499823]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x8089a)[0x7f769b49989a]
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z24deserialize_ft_versionediP4rbufPP2ftj+0xc32)[0x7f769b525622]
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z24toku_deserialize_ft_fromi10__toku_lsnPP2ft+0x229)[0x7f769b525949]
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z35toku_read_ft_and_store_in_cachefileP9ft_handleP9cachefile10__toku_lsnPP2ft+0x76)[0x7f769b525bb6]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x11e20a)[0x7f769b53720a]
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z28toku_ft_handle_open_recoveryP9ft_handlePKciiP10cachetableP7tokutxn7FILENUM10__toku_lsn+0x2d)[0x7f769b53938d]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x1204aa)[0x7f769b5394aa]
/usr/lib64/mysql/plugin/ha_tokudb.so(_Z14tokuft_recoverP13__toku_db_envPFvS0_P7tokutxnEPFvS0_P10cachetableEP10tokuloggerPKcSC_PFiP9__toku_dbPK10__toku_dbtSH_EPFiSE_SH_SH_SH_PFvSH_PvESK_EPFiSE_SE_P9DBT_ARRAY
SQ_SH_SH_EPFiSE_SE_SQ_SH_SH_Em+0x2538)[0x7f769b5017b8]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x1107b0)[0x7f769b5297b0]
/usr/lib64/mysql/plugin/ha_tokudb.so(+0x5195f)[0x7f769b46a95f]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x6e4018]
/usr/sbin/mysqld[0x5b254d]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x833)[0x5b7573]
/usr/sbin/mysqld[0x51c638]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x47f)[0x52119f]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f769e590af5]
/usr/sbin/mysqld[0x518239]
Engine status function not available
Memory usage:
Arena 0:
system bytes = 0
in use bytes = 0
Total (incl. mmap):
system bytes = 0
in use bytes = 0
max mmap regions = 0
max mmap bytes = 0
150928 3:53:37 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Any ideas about how to fix this issue?
Follow ups