I wonder if this could be caused by missing MDL protection around TRUNCATE TABLE, which would then incorrectly allow concurrent INSERT and TRUNCATE. One place where MDL is definitely missing is DROP DATABASE (reported as MDEV-11342 <https://jira.mariadb.org/browse/MDEV-11342>).
That said, the InnoDB in MariaDB 10.2 is based on MySQL 5.7, and one difference between MySQL 5.6 and 5.7 is that InnoDB supports crash-safe atomic TRUNCATE TABLE for .ibd files (WL#6501 <http://dev.mysql.com/worklog/task/?id=6501>). Best regards, Marko -- DON’T MISS M|17 April 11 - 12, 2017 The Conrad Hotel New York City https://m17.mariadb.com/ Marko Mäkelä, Lead Developer InnoDB MariaDB Corporation
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
