Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.6.4
-
None
-
Debian
Description
We had a mariadb crash today due to out of disk.
After restoring the server all CONNECT tables had become ENGINE=SEQUENCE in their definition.
Example schema:
CREATE TABLE `history` (
|
`itemid` bigint(20) unsigned NOT NULL, |
`clock` int(11) NOT NULL DEFAULT 0, |
`value` double(16,4) NOT NULL DEFAULT 0, |
`ns` int(11) NOT NULL DEFAULT 0 |
) ENGINE=CONNECT DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin `table_type`=MYSQL `option_list`='connect=mysql://[...]' |
PARTITION BY RANGE (`clock`)
|
(PARTITION `p202202042100` VALUES LESS THAN (1644012000) ENGINE = CONNECT, |
[...])
|
After crash:
CREATE TABLE `history` (
|
`itemid` bigint(20) unsigned NOT NULL, |
`clock` int(11) NOT NULL DEFAULT 0, |
`value` double(16,4) NOT NULL DEFAULT 0, |
`ns` int(11) NOT NULL DEFAULT 0 |
) ENGINE=SEQUENCE DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin `table_type`=MYSQL `option_list`='connect=mysql://[...]' |
PARTITION BY RANGE (`clock`)
|
(PARTITION `p202202042100` VALUES LESS THAN (1644012000) ENGINE = CONNECT, |
[...])
|
I've checked a few things, the frm file has a refernce to CONNECT and the header doesnt indicate a Sequence either.
00000020: 0005 0000 0000 2e00 0000 0000 0000 0010 |
My guess is that it's the table repair process?