maria-discuss team mailing list archive

[Sergei Golubchik <serg@xxxxxxxxxxx>]

Hi, Fernando!

On Sep 28, Fernando Marcelo wrote:
> 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)

This is an internal tokudb assertion.
I'd say it's *very* unlikely that anything we've done in MariaDB
could've caused this assertion.

But MariaDB-5.5.41 included tokudb-7.5.3, and MariaDB-5.5.44 included
tokudb-7.5.7. It's quite possible that some tokudb change between 7.5.3
and 7.5.7 is the reason.

Regards,
Sergei