mirror of
https://github.com/MariaDB/server.git
synced 2025-10-12 12:25:37 +03:00
243f829c1c
If we have a 2+ node cluster which is replicating from an async master and the binlog_format is set to STATEMENT and multi-row inserts are executed on a table with an auto_increment column such that values are automatically generated by MySQL, then the server node generates wrong auto_increment values, which are different from what was generated on the async master. In the title of the MDEV-9519 it was proposed to ban start slave on a Galera if master binlog_format = statement and wsrep_auto_increment_control = 1, but the problem can be solved without such a restriction. The causes and fixes: 1. We need to improve processing of changing the auto-increment values after changing the cluster size. 2. If wsrep auto_increment_control switched on during operation of the node, then we should immediately update the auto_increment_increment and auto_increment_offset global variables, without waiting of the next invocation of the wsrep_view_handler_cb() callback. In the current version these variables retain its initial values if wsrep_auto_increment_control is switched on during operation of the node, which leads to inconsistent results on the different nodes in some scenarios. 3. If wsrep auto_increment_control switched off during operation of the node, then we must return the original values of the auto_increment_increment and auto_increment_offset global variables, as the user has set. To make this possible, we need to add a "shadow copies" of these variables (which stores the latest values set by the user). https://jira.mariadb.org/browse/MDEV-9519
32 lines
1.5 KiB
Modula-2
32 lines
1.5 KiB
Modula-2
##############################################################################
|
|
#
|
|
# List the test cases that are to be disabled temporarily.
|
|
#
|
|
# Separate the test case name and the comment with ':'.
|
|
#
|
|
# <testcasename> : MDEV-<xxxx> <comment>
|
|
#
|
|
# Do not use any TAB characters for whitespace.
|
|
#
|
|
##############################################################################
|
|
|
|
galera_flush : MariaDB does not have global.thread_statistics
|
|
galera_account_management : MariaDB 10.0 does not support ALTER USER
|
|
galera_binlog_rows_query_log_events: MariaDB does not support binlog_rows_query_log_events
|
|
galera_migrate : MariaDB does not support START SLAVE USER
|
|
galera_as_master_gtid : Requires MySQL GTID
|
|
galera_as_master_gtid_change_master : Requires MySQL GTID
|
|
galera_as_slave_preordered : wsrep-preordered feature not merged to MariaDB
|
|
GAL-419 : MDEV-13549 Galera test failures
|
|
galera_var_notify_cmd : MDEV-13549 Galera test failures
|
|
galera_as_slave_replication_bundle : MDEV-13549 Galera test failures
|
|
galera_ssl_upgrade : MDEV-13549 Galera test failures
|
|
galera.MW-329 : wsrep_local_replays not stable
|
|
MW-416 : MDEV-13549 Galera test failures
|
|
MW-388 : MDEV-13549 Galera test failures
|
|
galera_sst_mysqldump_with_key : MDEV-16890 Galera test failure
|
|
galera_gc_fc_limit : MDEV-17061 Test failure on galera.galera_gc_fc_limit
|
|
galera_as_slave_replication_budle : MDEV-15785 Test case galera_as_slave_replication_bundle caused debug assertion
|
|
galera_wan : MDEV-17259: Test failure on galera.galera_wan
|
|
galera_pc_ignore_sb : MDEV-17357 Test failure on galera.galera_pc_ignore_sb
|