Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 10.0.17-galera, 5.5.43
-
Fix Version/s: 5.5.44-galera, 10.0.20-galera
-
Component/s: Galera
-
Labels:
Description
This is reproducible everytime. Doing a CREATE from SELECT, and then adding INDEX on column results in crashing of all other servers in Galera cluster.
I have attached my.cnf MariaDB configuration, and the test setup is simple consiting of three servers. Execute this on one of the servers:
CREATE DATABASE foobar;
USE foobar;
CREATE TABLE foo (
timestamp int(11) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
INSERT INTO foo (timestamp) VALUES (1), (2), (3);
CREATE TABLE bar (timestamp INT) SELECT timestamp FROM foo; ALTER TABLE bar ADD INDEX tind (timestamp);
And all the rest of the servers will crash. I have attached relevant log files. Take a look at server.2.log or server.3.log.
Some widely used software (ie Drupal's Views Data Export module) uses this statements, which is how we encountered this bug.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
https://github.com/MariaDB/server/commit/0bfae356d4f774c939a5642cd19ee6bfc682b8e7.patch