summaryrefslogtreecommitdiff
path: root/mysql-test/suite/galera_sr
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.4 into 10.5Marko Mäkelä2021-04-082-0/+57
|\
| * MDEV-25226 Assertion when wsrep_on set OFF with SR transactionDaniele Sciascia2021-04-052-0/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch makes the following changes around variable wsrep_on: 1) Variable wsrep_on can no longer be updated from a session that has an active transaction running. The original behavior allowed cases like this: BEGIN; INSERT INTO t1 VALUES (1); SET SESSION wsrep_on = OFF; INSERT INTO t1 VALUES (2); COMMIT; With regular transactions this would result in no replication events (not even value 1). With streaming replication it would be unnecessarily complex to achieve the same behavior. In the above example, it would be possible for value 1 to be already replicated if it happened to fill a separate fragment, while value 2 wouldn't. 2) Global variable wsrep_on no longer affects current sessions, only subsequent ones. This is to avoid a similar case to the above, just using just by using global wsrep_on instead session wsrep_on: --connection conn_1 BEGIN; INSERT INTO t1 VALUES(1); --connection conn_2 SET GLOBAL wsrep_on = OFF; --connection conn_1 INSERT INTO t1 VALUES(2); COMMIT; The above example results in the transaction to be replicated, as global wsrep_on will only affect the session wsrep_on of new connections. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Disable crashing Galera tests: MDEV-18534, MDEV-24485Marko Mäkelä2021-03-191-0/+1
| |
* | Merge 10.4 into 10.5Marko Mäkelä2021-03-191-2/+1
|\ \ | |/
| * Disable failing Galera testsMarko Mäkelä2021-03-191-2/+1
| |
* | Update disabled.def in suitesJan Lindström2021-01-271-0/+2
| | | | | | | | | | | | * galera * galera_sr * galera_3nodes
* | Merge 10.4 into 10.5Marko Mäkelä2021-01-253-12/+9
|\ \ | |/
| * MDEV-18542 : galera_sr.galera-features#56: Test failure: signal 6; ↵Jan Lindström2021-01-133-12/+9
| | | | | | | | | | | | mysqltest: Can't connect to local MySQL server Make test faster
* | Merge 10.4 into 10.5Marko Mäkelä2021-01-111-0/+3
|\ \ | |/
| * MDEV-24500: Added wait condition to make sure table t1 is replicated to node_2.bb-10.4-MDEV-24500Stepan Patryshev2021-01-041-0/+3
| |
* | Merge 10.4 into 10.5Marko Mäkelä2020-10-302-0/+76
|\ \ | |/
| * MDEV-23623 - Fix assertion in MTR test galera_sr.GCF-1051Daniele Sciascia2020-10-282-0/+76
| | | | | | | | | | | | | | | | | | | | | | | | Fix assertion `thd->in_active_multi_stmt_transaction() || thd->m_transaction_psi == __null' failed on MTR test galera_sr.GCF-1051. Add a new MTR test MDEV-23623 that reproduces the issue deterministically and update wsrep-lib submodule, containing the actual fix. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Merge 10.4 into 10.5Marko Mäkelä2020-09-237-81/+14
|\ \ | |/
| * MDEV-23659 : Update Galera disabled.def fileJan Lindström2020-09-221-2/+0
| |
| * MDEV-21170 : Galera test failure on galera_sr.GCF-1043[A|B]Jan Lindström2020-09-224-68/+0
| | | | | | | | | | | | Add error printout when mysql.wsrep_streaming_log lock fails. However, tests are very undeterministic and not suitable for mtr environment. Thus, they are removed.
| * MDEV-23617 : galera_sr.galera_sr_rollback_retry MTR failed: 1213: Deadlock ↵Jan Lindström2020-09-142-11/+14
| | | | | | | | | | | | | | found when trying to get lock Add corrected wait_condition to wait until rows are in streaming replication log.
* | Merge 10.4 into 10.5Marko Mäkelä2020-09-096-29/+70
|\ \ | |/
| * MDEV-23608 : galera_sr.GCF-597 MTR failed: query 'ROLLBACK' succeeded - ↵Jan Lindström2020-09-092-1/+20
| | | | | | | | | | | | should have failed with errno 1213 Added wait_condition to wait correct streaming state.
| * MDEV-23611 : galera_sr.galera_sr_kill_query MTR failed: 15 instead of 0 on ↵Jan Lindström2020-09-092-6/+23
| | | | | | | | | | | | "SELECT COUNT(*) AS EXPECT_0 FROM mysql.wsrep_streaming_log;" Add wait_condition to stabilize test.
| * MDEV-23613 : galera_sr.galera_sr_kill_slave MTR failed: query 'LOCK TABLE t2 ↵Jan Lindström2020-09-092-22/+27
| | | | | | | | | | | | | | WRITE' failed: 1146: Table 'test.t2' doesn't exist Remove unnecessary sleeps from test and replace them with proper wait_conditions.
* | Merge 10.4 into 10.5Marko Mäkelä2020-08-011-0/+3
|\ \ | |/
| * Update Galera global warning ignore list.Jan Lindström2020-07-241-0/+3
| |
* | Merge 10.4 into 10.5Marko Mäkelä2020-05-312-0/+31
|\ \ | |/
| * MDEV-22616 CHECK TABLE fails with wsrep_trx_fragment_size > 0 (#1551)Daniele Sciascia2020-05-212-0/+31
| | | | | | | | | | | | | | | | | | Executing CHECK TABLE with streaming replication enabled reports error "Streaming replication not supported with binlog_format=STATEMENT". Administrative commands such as CHECK TABLE, are not replicated and temporarily set binlog format to statement. To avoid the problem, report the error only for active transactions for which streaming replication is enabled.
* | Merge 10.4 into 10.5Marko Mäkelä2020-05-131-0/+27
|\ \ | |/
| * MDEV-22466 : Galera missing .test or .result filesJan Lindström2020-05-071-0/+27
| | | | | | | | Add missing .test and .result files.
* | Merge 10.4 into 10.5Marko Mäkelä2020-04-291-9/+4
|\ \ | |/
| * MDEV-18565 Galera mtr-suite fails if galera library is not installedSergei Golubchik2020-04-271-9/+4
| | | | | | | | | | | | revert/simplify f5390eea9a9 remove galera-specific checks from mtr and the main suite
* | Merge 10.4 into 10.5Marko Mäkelä2020-04-084-6/+6
|\ \ | |/
| * MDEV-22021: Galera database could get inconsistent with rollback to savepointDaniele Sciascia2020-03-314-6/+6
| | | | | | | | | | When binlog is disabled, WSREP will not behave correctly when SAVEPOINT ROLLBACK is executed and we will not rollback transaction.
* | Merge 10.4 into 10.5Marko Mäkelä2020-03-213-0/+287
|\ \ | |/
| * MDEV-21675: Data inconsistency after multirow insert rollback (#1474)Daniele Sciascia2020-03-213-0/+287
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove dead code * MDEV-21675 Data inconsistency after multirow insert rollback This patch fixes data inconsistencies that happen after rollback of multirow inserts, with binlog disabled. For example, statements such as `INSERT INTO t1 VALUES (1,'a'),(1,'b')` that fail with duplicate key error. In such cases the whole statement is rolled back. However, with wsrep_emulate_binlog in effect, the IO_CACHE would not be truncated, and the pending rows events would be replicated to the rest of the cluster. In the above example, it would result in row (1,'a') being replicated, whereas locally the statement is rolled back entirely. Making the cluster inconsistent. The patch changes the code so that prior to statement rollback, pending rows event are removed and the stmt cache reset. That patch also introduces MTR tests that excercise multirow insert statements for regular, and streaming replication.
| * MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-161-27/+0
| | | | | | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names This should not be merged upwards.
| * MDEV-21517 : Galera test galera_sr.GCF-561 failure: Result length mismatchJan Lindström2020-02-162-5/+10
| | | | | | | | Add wait conditions.
| * MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-165-264/+3
| | | | | | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names This should not be merged upwards.
* | MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-211-27/+0
| | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names
* | MDEV-21517 : Galera test galera_sr.GCF-561 failure: Result length mismatchJan Lindström2020-02-212-5/+10
| | | | | | | | Add wait conditions.
* | MDEV-21601 : Cleanup Galera disabled testsJan Lindström2020-02-215-264/+3
| | | | | | | | | | | | | | | | * Remove those tests that will not be supported on that release. * Make sure that correct tests are disabled and have MDEVs * Sort test names This should not be merged upwards.
* | Merge 10.4 into 10.5Marko Mäkelä2020-01-201-2/+17
|\ \ | |/
| * Disable Galera tests failing on bb and Azure until they are fixed.Jan Lindström2020-01-181-2/+17
| |
* | Merge 10.4 into 10.5Marko Mäkelä2019-12-163-12/+0
|\ \ | |/
| * MDEV-20780 Fixes for failures on galera_sr_ddl_master (#1425)Daniele Sciascia2019-12-113-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Test galera_sr_ddl_master would sometimes fail due to leftover streaming replication fragments. Rollbacker thread would attempt to open streaming_log table to remove the fragments, but would fail in check_stack_overrun(). Ultimately the check_stack_overrun() failure was caused by rollbacker missing to switch the victim's THD thread stack to rollbacker's thread stack. Also in this patch: - Remove duplicate functionality in rollbacker helper functions, and extract rollbacker fragment removal into function wsrep_remove_streaming_fragments() - Reuse open_for_write() in wsrep_schema::remove_fragments - Partially revert changes to galera_sr_ddl_master test from commit 44a11a7c085f4f5a4042100df0828d54d596103d. Removed unnecessary wait condition and isolation level setting
| * MDEV-20848 Fixes for MTR test galera_sr.GCF-1060 (#1421)Daniele Sciascia2019-12-041-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch contains two fixes: * wsrep_handle_mdl_conflict(): handle the case where SR transaction is in aborting state. Previously, a BF-BF conflict was reported, and the process would abort. * wsrep_thd_bf_abort(): do not restore thread vars after calling wsrep_bf_abort(). Thread vars are already restored in wsrep-lib if necessary. This also removes the assumption that the caller of wsrep_thd_bf_abort() is the given bf_thd, which is not the case. Also in this patch: * Remove unnecessary check for active victim transaction in wsrep_thd_bf_abort(): the exact same check is performed later in wsrep_bf_abort(). * Make wsrep_thd_bf_abort() and wsrep_log_thd() const-correct. * Change signature of wsrep_abort_thd() to take THD pointers instead of void pointers.
* | Merge 10.4 into 10.5Marko Mäkelä2019-11-291-0/+3
|\ \ | |/
| * Disable failing Galera test cases.Jan Lindström2019-11-291-0/+3
| |
* | MDEV-20907 Set innodb_log_files_in_group=1 by defaultMarko Mäkelä2019-10-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | Historically, InnoDB split the redo log into at least 2 files. MDEV-12061 allowed the minimum to be innodb_log_files_in_group=1, but it kept the default at innodb_log_files_in_group=2. Because performance seems to be slightly better with only one log file, and because implementing an append-only variant of the log would require a single file, let us define the default to be 1, and have innodb_log_file_size=96M, to retain the same default total size.
* | Merge 10.4 into 10.5Marko Mäkelä2019-10-2812-78/+179
|\ \ | |/
| * Add wait_condition to stabilize.Jan Lindström2019-10-252-24/+26
| |
| * Stabilize tests.Jan Lindström2019-10-2310-54/+153
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes to be committed: modified: mysql-test/suite/galera_sr/disabled.def modified: mysql-test/suite/galera_sr/r/GCF-561.result modified: mysql-test/suite/galera_sr/r/galera_sr_ddl_master.result modified: mysql-test/suite/galera_sr/r/galera_sr_kill_query.result modified: mysql-test/suite/galera_sr/r/galera_sr_shutdown_slave.result new file: mysql-test/suite/galera_sr/suite.pm modified: mysql-test/suite/galera_sr/t/GCF-561.test modified: mysql-test/suite/galera_sr/t/galera_sr_ddl_master.test modified: mysql-test/suite/galera_sr/t/galera_sr_kill_query.test modified: mysql-test/suite/galera_sr/t/galera_sr_shutdown_slave.test
* | Merge 10.4 into 10.5Marko Mäkelä2019-10-113-25/+48
|\ \ | |/
View Lorry Controller Status