Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not a Bug
-
10.1.21
-
RHEL 6.8
Description
Hello,
I tried to import today a mysqldump in a 10.1.21 MariaDB server that I exported from a 10.0.28 MariaDB server.
Apparently there were characters inside the dumpfile that made MariaDB crash :
[root@s-mysql-pp tmp]# mysql -p -D mydatabse < /tmp/database.sql
ERROR 2006 (HY000) at line 1264: MySQL server has gone away
I just had to remove those lines with sed (luckily thoses lines were web cache which I could spare) and then the import went well.
sed -i '/INSERT INTO `fe_session_data` VALUES.*/d' /tmp/database.sql
sed -i '/INSERT INTO `cf_cache_pages` VALUES.*/d' /tmp/database.sql
So back to the main problem, the first line that triggered the problem has a weight of 17398191 Bytes (which is quite a lot). I zipped that line and added it to the ticket.
That line is inserted in a table that is created this way :
DROP TABLE IF EXISTS `fe_session_data`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `fe_session_data` (
`hash` varchar(32) NOT NULL DEFAULT '',
`content` mediumblob,
`tstamp` int(11) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`hash`),
KEY `tstamp` (`tstamp`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;
So what I suppose is that the MariaDB 10.0.28 server somehow allowed to put too much stuff in the mediumblob (over 17.3 million chars, while the maximum should be 16777215) and that it's now impossible to import it inside a mariadb 10.1.21 database.
If you need the whole dump I can provide it to you, but it's about 800MB...