I've been a proudly user of mariadb 5.5.x for a long time now but given the nice feature setI decided to give mariadb 10.x a try.
I took one of our current slaves running mariadb 5.5.x (on centos 6.5) and followed the upgrade steps using yum and ran *mysql_upgrade*. The upgrade ran without any trouble...then I moved a huge table (about 1B records right now) from InnoDB to TokuDB.
Now, every couple of hours I find that the replication is far behind the master and the reason is because this server keeps checking tables marked as crashed....
I can't seems to find any indicator of OOM killer in the system logs NOR anything related to that in the mysql log, the only clue I have is:
--------------- 150303 10:08:57 mysqld_safe Number of processes running now: 0
150303 10:08:57 mysqld_safe mysqld restarted
150303 10:08:58 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
150303 10:08:59 [Warning] option 'innodb-status-file': boolean value 'ib_status' wasn't recognized. Set to OFF.
150303 10:08:59 [Warning] option 'innodb-autoextend-increment': unsigned value 10485760 adjusted to 1000
150303 10:08:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150303 10:08:59 [Note] InnoDB: The InnoDB memory heap is disabled
150303 10:08:59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150303 10:08:59 [Note] InnoDB: Memory barrier is not used
150303 10:08:59 [Note] InnoDB: Compressed tables use zlib 1.2.3
150303 10:08:59 [Note] InnoDB: Using Linux native AIO
150303 10:08:59 [Note] InnoDB: Using CPU crc32 instructions
150303 10:08:59 [Note] InnoDB: Initializing buffer pool, size = 6.0G
150303 10:08:59 [Note] InnoDB: Completed initialization of buffer pool
150303 10:08:59 [Note] InnoDB: Highest supported file format is Barracuda.
150303 10:08:59 [Note] InnoDB: Log scan progressed past the checkpoint lsn 14178608217047
150303 10:08:59 [Note] InnoDB: Database was not shutdown normally!