mirror of
https://github.com/MariaDB/server.git
synced 2025-09-16 16:42:28 +03:00
4601e6e565
Under ps-protocol, commandsl like COM_STMT_FETCH, COM_STMT_CLOSE and COM_STMT_SEND_LONG_DATA are not supposed to return errors. Therefore, if a transaction is BF aborted and the client is processing one of those commands, then we should not return a deadlock error immediately. Instead wait for the a subsequent client interaction which permits errors to be returned. To handle this, wsrep_before_command() now accepts parameter keep_command_error. If set true, keep_command_error will cause wsrep-lib side to skip result handling, and to keep the current error for the next interaction with the client. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
17 lines
495 B
Plaintext
17 lines
495 B
Plaintext
connection node_2;
|
|
connection node_1;
|
|
CREATE TABLE t1 (f1 INTEGER PRIMARY KEY, f2 CHAR(6)) ENGINE=InnoDB;
|
|
connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
|
|
connection node_2;
|
|
START TRANSACTION;
|
|
INSERT INTO t1 VALUES (1,'node_2');
|
|
connection node_1;
|
|
INSERT INTO t1 VALUES (1,'node_1');
|
|
connection node_2a;
|
|
connection node_2;
|
|
INSERT INTO t1 VALUES (2, 'node_2');
|
|
ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
|
|
wsrep_local_aborts_increment
|
|
1
|
|
DROP TABLE t1;
|