summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Adjust galera.query_cache test.bb-10.1-MDEV-13871Jan Lindström2018-09-222-16/+0
|
* Disable failing galera_wan test case.Jan Lindström2018-09-211-1/+1
|
* Fix galera.galera_wan test.Jan Lindström2018-09-202-0/+3
|
* Remove tests from disabled.Jan Lindström2018-09-201-3/+1
|
* Second bb runJan Lindström2018-09-200-0/+0
|
* MDEV-15805: Test failure on galera.query_cacheJan Lindström2018-09-203-36/+119
| | | | | Reset query cache after every test case and add wait after load infile.
* MDEV-13873: galera.galera_suspend_slave failed in buildbot with wrong error codeJan Lindström2018-09-192-0/+5
| | | | Add wsrep_sync_wait as we want INSERT to fail.
* MDEV-13871: galera.galera_unicode_identifiers failed in buildbot with ↵Jan Lindström2018-09-192-6/+12
| | | | | | 'Unknown database' Wait in second node until tables with databases are created.
* MDEV-17208: Test failure on galera.MW-286Jan Lindström2018-09-192-4/+5
| | | | Test changes only.
* Removed duplicate tests.Igor Babaev2018-09-193-151/+0
|
* Test galera.query_cache is still failing on bb.Jan Lindström2018-09-171-1/+1
|
* MDEV-17206: Test failure on galera.galera_ist_* in debug buildsbb-10.1-MDEV-13879Jan Lindström2018-09-174-0/+415
| | | | | Failure is due missing .rdiff files for debug build as tests have @have_debug combination.
* MDEV-13879: galera.galera_wan fails in buildbot with Stray state UUID msg or ↵Jan Lindström2018-09-173-6/+13
| | | | | | | with "Transport endpoint is not connected" or with a failure to start a node Add correct suppressions and wait conditions for expected database contents.
* Adjust Galera disabled tests based on test results.Jan Lindström2018-09-171-3/+0
|
* MDEV-14143: galera.galera_kill_smallchanges, galera.galera_kill_ddl fail in ↵Jan Lindström2018-09-145-1/+6
| | | | | | buildbot with "Last Applied Action message in non-primary configuration from member 0" Add supression.
* Test galera_sst_rsync_data_dir has different result on releaseJan Lindström2018-09-141-0/+103
| | | | | | | | | | and debug builds. Modified version for 10.1 from following commit: commit 8e68876477eaec7944baa0b63ef26e551693c4f8 Author: Oleksandr Byelkin <sanja@mariadb.com> Date: Thu Sep 13 15:06:44 2018 +0200 Fix of the test which has debug version
* MDEV-13876: galera.MW-328A failed in buildbot with wrong result or timeoutJan Lindström2018-09-144-3/+3
| | | | | Move MW-328[A,B,C] to big tests as there seem to be big variation on their execution times and sometimes that could lead timeout.
* MDEV-16912: Spider Order By column[datatime] limit 5 returns 3 rowsJacob Mathew2018-09-136-0/+233
| | | | | | | | | | | | | | | | | | | | | The problem occurs in 10.2 and earlier releases of MariaDB Server because the Partition Engine was not pushing the engine conditions to the underlying storage engine of each partition. This caused Spider to return the first 5 rows in the table with the data provided by the customer. 2 of the 5 rows did not qualify the WHERE clause, so they were removed from the result set by the server. To fix the problem, I have back-ported support for engine condition pushdown in the Partition Engine from MariaDB Server 10.3. Author: Jacob Mathew. Reviewer: Kentoku Shiba. Cherry-Picked: Commit eb2ca3d on branch bb-10.2-MDEV-16912
* try to fix version detectionOleksandr Byelkin2018-09-131-2/+2
|
* Merge pull request #865 from grooverdan/MDEV-17173-wsrep_sstJan Lindström2018-09-131-3/+12
|\ | | | | MDEV-17173: correct parsing of 12.13.14.15:4444/xtrabackup_sst leavin…
| * MDEV-17173: correct parsing of 12.13.14.15:4444/xtrabackup_sst leaving ↵Daniel Black2018-09-131-3/+12
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LSN/SST_VER blank Correcting commit e78e308e818 $ . scripts/wsrep_sst_common.sh --address 12.13.14.15:4444/xtrabackup_sst ; set | grep WSREP_SST WSREP_SST_OPT_ADDR=12.13.14.15:4444/xtrabackup_sst WSREP_SST_OPT_ADDR_PORT=4444 WSREP_SST_OPT_AUTH= WSREP_SST_OPT_BINLOG= WSREP_SST_OPT_BINLOG_INDEX= WSREP_SST_OPT_BYPASS=0 WSREP_SST_OPT_CONF=' ' WSREP_SST_OPT_DATA= WSREP_SST_OPT_DEFAULT= WSREP_SST_OPT_EXTRA_DEFAULT= WSREP_SST_OPT_HOST=12.13.14.15 WSREP_SST_OPT_HOST_UNESCAPED=12.13.14.15 WSREP_SST_OPT_LSN= WSREP_SST_OPT_MODULE=xtrabackup_sst WSREP_SST_OPT_PATH=xtrabackup_sst WSREP_SST_OPT_PORT=4444 WSREP_SST_OPT_PSWD= WSREP_SST_OPT_SST_VER= WSREP_SST_OPT_SUFFIX_DEFAULT= WSREP_SST_OPT_SUFFIX_VALUE= WSREP_SST_OPT_USER= . scripts/wsrep_sst_common.sh --address 12.13.14.15:4444/xtrabackup_sst/1234/5676 ; set | grep WSREP_SST WSREP_SST_OPT_ADDR=12.13.14.15:4444/xtrabackup_sst/1234/5676 WSREP_SST_OPT_ADDR_PORT=4444 WSREP_SST_OPT_AUTH= WSREP_SST_OPT_BINLOG= WSREP_SST_OPT_BINLOG_INDEX= WSREP_SST_OPT_BYPASS=0 WSREP_SST_OPT_CONF=' ' WSREP_SST_OPT_DATA= WSREP_SST_OPT_DEFAULT= WSREP_SST_OPT_EXTRA_DEFAULT= WSREP_SST_OPT_HOST=12.13.14.15 WSREP_SST_OPT_HOST_UNESCAPED=12.13.14.15 WSREP_SST_OPT_LSN=1234 WSREP_SST_OPT_MODULE=xtrabackup_sst WSREP_SST_OPT_PATH=xtrabackup_sst/1234/5676 WSREP_SST_OPT_PORT=4444 WSREP_SST_OPT_PSWD= WSREP_SST_OPT_SST_VER=5676 WSREP_SST_OPT_SUFFIX_DEFAULT= WSREP_SST_OPT_SUFFIX_VALUE= WSREP_SST_OPT_USER=
* Fix test galera#505 galera library version check.Jan Lindström2018-09-121-14/+8
| | | | Test requires galera library version 25.3.24.
* MDEV-17155: Incorrect ORDER BY optimization: full index scan is used instead ↵Sergei Petrunia2018-09-121-0/+19
| | | | | | | | | | | | | | | | | | | | | of range The bug was this scenario: 1. Join optimizer picks a range plan on index IDX1 (This index doesn't match the ORDER BY clause, so sorting will be needed) 2. Index Condition Pushdown pushes a part of WHERE down. The pushed condition is removed from SQL_SELECT::cond 3. test_if_skip_sort_order() figures that it's better to use IDX2 (as it will match ORDER BY ... LIMIT and so will execute faster) 3.1 It sees that there was a possible range access on IDX2. It tries to construct it by calling SQL_SELECT::test_quick_select(), but alas, SQL_SELECT::cond doesn't have all parts of WHERE anymore. So it uses full index scan which is slow. (The execution works fine because there's code further in test_if_skip_sort_order() which "Unpushes" the index condition and restores the original WHERE clause. It was just the test_quick_select call that suffered).
* Update disabled Galera tests.Jan Lindström2018-09-121-2/+13
|
* MDEV-17108: Test failure on galera.galera_kill_ddlJan Lindström2018-09-122-0/+3
| | | | Add suppression.
* MDEV-13743: galera_toi_truncate may fail with: query 'reap' succeeded - ↵Jan Lindström2018-09-122-3/+15
| | | | | | | should have failed with errno 1213 Replace sleep with debug sync point before insert commit to make sure insert is not executed before truncate has started.
* MDEV-15845 Test failure on galera.galera_concurrent_ctasmkaruza2018-09-121-0/+4
| | | | While executing CTAS galera applier thread can cause CTAS to abort and rollback. Rollback can take time causing applier thread to shutdown node after serial unsuccessful retries to apply transaction. Don't set lock_wait_timeout to zero to wait for lock.
* MDEV-12956 provide default datadir for mariabackup --copy-backVladislav Vaintroub2018-09-111-2/+33
| | | | | | | | On Unix, it is compiled-in datadir value. On Windows, the directory is ..\data, relative to directory mariabackup.exe server uses the same logic to determine datadir.
* MDEV-17106: Test failure on galera.galera_binlog_stmt_autoincJan Lindström2018-09-113-2/+378
| | | | | Add missing test case with proper wait conditions for expected node contents.
* MDEV-17151: Galera test failure on galera.galera_var_node_addressbb-10.1-MDEV-17151Jan Lindström2018-09-102-2/+8
| | | | Add wait_conditions to wait expected node contents.
* MDEV-17143: Galera test failure on galera.MW-44Jan Lindström2018-09-093-16/+13
| | | | | Start general log OFF and then truncate mysql.general_log and use proper wait timeouts to make sure it is really empty.
* bump the VERSIONDaniel Bartholomew2018-09-081-1/+1
|
* Add one more wait for truncate in MW-44.Jan Lindström2018-09-082-0/+15
|
* Merge branch 'bb-10.1-release' into 10.1Sergei Golubchik2018-09-07270-195032/+5670
|\
| * remove doubly-installed fileSergei Golubchik2018-09-071-5/+0
| |
| * Updated list of unstable tests for 10.1.36 releasemariadb-10.1.36Elena Stepanova2018-09-071-80/+38
| |
| * Merge branch '10.0-galera' into 10.1Sergei Golubchik2018-09-0719-139/+570
| |\
| | * bump the VERSIONDaniel Bartholomew2018-08-071-1/+1
| | |
| | * Add wsrep.cnfmariadb-galera-10.0.36Jan Lindström2018-08-041-0/+6
| | |
| | * Add galera library dependency directly to test case.Jan Lindström2018-08-032-1/+16
| | |
| | * MariaDB adjustments.Jan Lindström2018-08-032-3/+16
| | |
| | * Also include InnoDB undo tablespaces in rsync sstVasil Dimov2018-08-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | If --innodb-undo-tablespaces is used, then InnoDB stores undo in a separate file(s) which whould also be replicated. This fixes Issue#337 This filter will cause sst failed at applying undo... https://github.com/codership/mysql-wsrep/issues/337
| | * Put one filter per line in wsrep_sst_rsync.shVasil Dimov2018-08-031-2/+8
| | | | | | | | | | | | | | | This way it is more readable and easy to change, also if a new entry is added or one removed, the diff will be easier to read.
| | * galera#505 mtr testmkaruza2018-08-032-0/+22
| | | | | | | | | | | | MTR test for galera#505
| | * codership/galera#501 Check cluster weight in galera_pc_weight testTeemu Ollakka2018-08-032-32/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Check that cluster weight have proper values in galera_pc_weight test. Removed sleeps from tests and added condition waits for expected cluster sizes. Replaced galera suspend/resume with gmcast.isolate in order to avoid breaking client connections to server which is isolated from the cluster and to avoid the need to reset wsrep_cluster_address. Re-recorded galera_defaults.
| | * Add missing WSREP(thd) condition and remove unnecessary DBUG_RETURN.Jan Lindström2018-08-021-3/+2
| | |
| | * Merge remote-tracking branch 'origin/5.5-galera' into 10.0-galeraJan Lindström2018-08-026-98/+369
| | |\
| | | * Follow up to previous commit for codership/mysql-wsrep#332mariadb-galera-5.5.61Daniele Sciascia2018-08-021-1/+1
| | | | | | | | | | | | | | | | Fix misplaced `DBUG_RETURN` in `Alter_table_statement::execute`.
| | | * Fix FK constraint violation in applier, after ALTER TABLE ADD FKDaniele Sciascia2018-08-027-119/+380
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding a FK constraint to an existing table (ALTER TABLE ADD FOREIGN KEY) causes the applier to fail, if a concurrent DML statement that violate the new constraint (i.e. a DELETE or UPDATE of record in the parent table). For exmaple, the following scenario causes a crash in the applier: 1. ALTER successfully adds FK constraint in node_1 2. On node_2 is UPDATE is in pre_commit() and has certified successfully 3. ALTER is delivered in node_2 and BF aborts DML 4. Applying UPDATE event causes FK violation in node_1 To avoid this situation it is necessary for UPDATE to fail during certification. And for the UPDATE to fail certfication it is necessary that ALTER appends certification keys for both the child and the parent table. Before this patch, ALTER TABLE ADD FK only appended keys for child table which is ALTERed.
| | | * Merge tag 'mariadb-5.5.61' into 5.5-galeraJan Lindström2018-08-01120-281/+2237
| | | |\
View Lorry Controller Status