mirror of
https://github.com/MariaDB/server.git
synced 2025-02-09 23:24:11 +01:00
daaa16a47f
Problem is that Galera starts TOI (total order isolation) i.e. it sends query to all nodes. Later it is discovered that used engine or other feature is not supported by Galera. Because TOI is executed parallelly in all nodes appliers could execute given TOI and ignore the error and start inconsistency voting causing node to leave from cluster or we might have a crash as reported. For example SEQUENCE engine does not support GEOMETRY data type causing either inconsistency between nodes (because some errors are ignored on applier) or crash. Fixed my adding new function wsrep_check_support to check can Galera support provided CREATE TABLE/SEQUENCE before TOI is started and if not clear error message is provided to the user. Currently, not supported cases: * CREATE TABLE ... AS SELECT when streaming replication is used * CREATE TABLE ... WITH SYSTEM VERSIONING AS SELECT * CREATE TABLE ... ENGINE=SEQUENCE * CREATE SEQUENCE ... ENGINE!=InnoDB * ALTER TABLE t ... ENGINE!=InnoDB where table t is SEQUENCE Signed-off-by: Julius Goryavsky <julius.goryavsky@mariadb.com>
12 lines
447 B
Text
12 lines
447 B
Text
connection node_2;
|
|
connection node_1;
|
|
SET GLOBAL wsrep_ignore_apply_errors=0;
|
|
SET SESSION AUTOCOMMIT=0;
|
|
SET SESSION max_error_count=0;
|
|
CREATE TABLE t0 (id GEOMETRY,parent_id GEOMETRY)ENGINE=SEQUENCE;
|
|
ERROR 42000: This version of MariaDB doesn't yet support 'non-InnoDB sequences in Galera cluster'
|
|
connection node_2;
|
|
SHOW CREATE TABLE t0;
|
|
ERROR 42S02: Table 'test.t0' doesn't exist
|
|
connection node_1;
|
|
SET GLOBAL wsrep_ignore_apply_errors=DEFAULT;
|