summaryrefslogtreecommitdiff
path: root/mysql-test/suite/galera_sr
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.4 into 10.5Marko Mäkelä2021-09-242-12/+8
|\
| * MDEV-26571 : galera_sr.GCF-627 MTR failed: Result length mismatchJan Lindström2021-09-232-12/+8
| | | | | | | | | | Test changes only: do not output mysql.wsrep_streaming_log contents.
* | Merge branch '10.4' into 10.5Monty2021-09-153-0/+63
|\ \ | |/ | | | | Fixed also an error in suite/perfschema/t/transaction_nested_events-master.opt
| * MDEV-21613 Failed to open table mysql.wsrep_streaming_log for writingbb-10.4-MDEV-21613Daniele Sciascia2021-09-143-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix sporadic failure for MTR test galera_sr.GCF-1018B. The test sometimes fails due to an error that is logged to the error log unnecessarily. A deterministic test case (included in this patch) shows that the error is loggen when a transaction is BF aborted right before it opens the streaming log table to perform fragment removal. When that happens, the attempt to open the table fails and consequently an error is logged. There is no need to log this error, as an ER_LOCK_DEADLOCK error is returned to the client. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Merge remote-tracking branch 'upstream/10.4' into 10.5Vicențiu Ciorbaru2021-09-103-0/+97
|\ \ | |/
| * MDEV-25718 Assertion `transaction.is_streaming()' failedDaniele Sciascia2021-09-063-0/+97
| | | | | | | | | | | | | | * Update wsrep-lib which contains the fix * Add deterministic test case that reproduces the assertion Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Merge 10.4 into 10.5Marko Mäkelä2021-08-182-0/+160
|\ \ | |/
| * MDEV-25717 Assertion `owning_thread_id_ == wsrep::this_thread::get_id()'Daniele Sciascia2021-08-182-0/+160
| | | | | | | | | | | | | | A test case to reproduce the issue. The actual fix is in galera library. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Merge 10.4 into 10.5Marko Mäkelä2021-06-014-8/+166
|\ \ | |/
| * MDEV-25769 : Galera test failure on galera_sr.GCF-627Jan Lindström2021-05-262-8/+11
| | | | | | | | Add wait_condition to wait until streaming log is empty.
| * MDEV-25551 applying crash with tables without PKsjaakola2021-05-262-0/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The underlying problem with MDEV-25551 turned out to be that transactions having changes for tables with no primary key, were not safe to apply in parallel. This is due to excessive locking in innodb side, and even non related row modifications could end up in lock conflict during applying. The fix for MDEV-25551 has disabled parallel applying for tables with no PK. This fix depends on change for wsrep-lib, where a separate PR allows application to modify transaction flags in wsrep-lib. This commit has also separate mtr test for verifying that transactions modifying a table with no primary key, will not apply in parallel. This test is a modified version of initial test created by Gabor Orosz, the reporterr of MDEV-25551. Another mtr test was added in galera_sr suite, for testing if modifying tables with no primary key would causes issues for streaming replication use cases. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | Merge 10.4 into 10.5Marko Mäkelä2021-05-036-19/+103
|\ \ | |/
| * MDEV-25553 : Avoid unnecessary rollbacks with SRbb-10.4-MDEV-25553Daniele Sciascia2021-04-286-19/+103
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch changes statement rollback for streaming replication. Previously, a statement rollback was turned into full transaction rollback in the case where the transaction had already replicated a fragment. This was introduced in the initial implementation of streaming replication due to the fact that we do not have a mechanism to perform a statement rollback on the applying side. This policy is however overly pessimistic, causing full rollbacks even in cases where a local statement rollback, would not require a statement rollback on the applying side. This happens to be case when the statement itself has not replicated any fragments. So the patch changes the condition that determines if a statement rollback should be turned into a full rollback accordingly. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | 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.
View Lorry Controller Status