summaryrefslogtreecommitdiff
path: root/mysql-test/suite/galera/include
Commit message (Collapse)AuthorAgeFilesLines
* Improve Galera SST testsbb-10.6-MDEV-25359Jan Lindström2021-04-185-253/+283
| | | | | | | | * Table should have primary key * Enable wsrep_sync_wait before final selects * Enable autocommit before final selects. * Fix joiner monitoring in case of mysqldump. * Add wait_conditions to stabilize
* Merge 10.4 into 10.5Marko Mäkelä2021-03-273-2/+2
|\
| * Merge 10.3 into 10.4Marko Mäkelä2021-03-273-2/+2
| |\
| | * Follow up fixes for making @@wsrep_provider read-onlyDaniele Sciascia2021-03-233-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove usage of wsrep_provider variable in galera_ist_restart_joiner * Rename galera_load_provider.inc and galera_unload_provider.inc to galera_stop_replication.inc and galera_start_replication.inc. Their original names were no longer reflecting what these include files do. followup for ce3a2a688db Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
| | * Merge branch 'bb-10.2-release' into 10.2Sergei Golubchik2021-02-222-3/+1
| | |\
| | * | MDEV-19950: Galera test failure on galera_ssl_upgradeJulius Goryavsky2021-02-111-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test requires adaptation for MariaDB, which is done in this patch. In addition, this patch includes a fix for the SST script startup code that adds escaping for special characters on the command line (in case they are contained in the arguments to mysqld). The fix does not require separate tests, as the required tests are already part of the mtr suite for Galera.
* | | | Merge branch 'bb-10.4-release' into bb-10.5-releasemariadb-10.5.9Sergei Golubchik2021-02-192-4/+1
|\ \ \ \ | |/ / /
| * | | Merge branch 'bb-10.3-release' into bb-10.4-releasemariadb-10.4.18Sergei Golubchik2021-02-192-4/+1
| |\ \ \ | | | |/ | | |/|
| | * | make @@wsrep_provider and @@wsrep_notify_cmd read-onlymariadb-10.2.37Sergei Golubchik2021-02-182-3/+1
| | |/ | | | | | | | | | this should simplify run-time cluster management
| | * Add missing file.Jan Lindström2020-10-101-0/+9
| | |
| | * MDEV-17585 : wsrep.variables failed in buildbot with deadlock on CREATE USERJan Lindström2020-10-101-9/+0
| | | | | | | | | | | | | | | Stabilize test by using correct galera library and restore original galera cluster at end.
* | | Merge 10.4 into 10.5Marko Mäkelä2020-09-041-7/+0
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-09-031-7/+0
| |\ \ | | |/
* | | Merge 10.4 into 10.5Marko Mäkelä2020-08-015-0/+29
|\ \ \ | |/ /
| * | Merge 10.3 into 10.4Marko Mäkelä2020-07-315-0/+29
| |\ \ | | |/
| | * MDEV-18177 : Galera test failure on galera_autoinc_sst_mariabackupJan Lindström2020-07-245-0/+29
| | | | | | | | | | | | Add wait_condition
* | | Merge 10.4 into 10.5Marko Mäkelä2020-04-291-0/+7
|\ \ \ | |/ /
| * | MDEV-18565 Galera mtr-suite fails if galera library is not installedSergei Golubchik2020-04-271-0/+7
| | | | | | | | | | | | | | | | | | revert/simplify f5390eea9a9 remove galera-specific checks from mtr and the main suite
| * | Merge 10.3 into 10.4Marko Mäkelä2020-04-221-0/+3
| |\ \ | | |/
| | * MDEV-22181 : galera.galera_sst_mysqldump_with_key MTR failed: INSERT failed: ↵Jan Lindström2020-04-221-0/+3
| | | | | | | | | | | | | | | | | | | | | 1146: Table 'test.t1' doesn't exist Add wait condition to make sure table test.t1 is replicated to node_2 before we insert to it.
| | * MDEV-18565: Galera mtr-suite fails if galera library is not installedJulius Goryavsky2019-07-173-11/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, running mtr with an incorrect (for example, new or obsolete) version of wsrep_provider (for example, with the 26 version of libgalera_smm.so) leads to the failure of tests in several suites with vague error diagnostics. As for the galera_3nodes suite, the mtr also does not effectively check all the prerequisites after merge with MDEV-18426 fixes. For example, tests that using mariabackup do not check for presence of ss and socat/nc. This is due to improper handling of relative paths in mtr scripts. In addition, some tests in different suites can be run without setting the environment variables such as MTR_GALERA_TFMT, XBSTREAM, and so on. To eliminate all these issues, this patch makes the following changes: 1. Added auxiliary wsrep_mtr_check utility (which located in the mysql-test/lib/My/SafeProcess subdirectory), which compares the versions of the wsrep API that used by the server and by the wsrep provider library, and it does this comparison safely, without accessing the API if the versions do not match. 2. All checks related to the presence of mariabackup and utilities that necessary for its operation transferred from the local directories of different mtr suites (from the suite.pm files) to the main suite.pm file. This not only reduces the amount of code and eliminates duplication of identical code fragments, but also avoids problems due to the inability of mtr to consider relative paths to include files when checking skip combinations. 3. Setting the values of auxiliary environment variables that are necessary for Galera, SST scripts and mariabackup (to work properly) is moved to the main mysql-test-run.pl script, so as not to duplicate this code in different suites, and to avoid partial corrections of the same errors for different suites (while other suites remain uncorrected). 4. Fixed duplication of the have_file_key_management.inc and have_filekeymanagement.inc files between different suites, these checks are also transferred to the top level. 5. Added garbd presence check and garbd path variable. https://jira.mariadb.org/browse/MDEV-18565
| | * MDEV-18426: Most of the mtr tests in the galera_3nodes suite failJulius Goryavsky2019-02-061-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most of the mtr tests in the galera_3nodes suite fail for a variety of reasons with a variety of errors. Some tests simply need to add the missing "connection" lines to the result files, but many of them fail due to substantial errors that require reworking test files. This patch adds the missing "connection" lines to the result files and fixes several substantial flaws in the galera_3nodes suite tests and in the mtr framework service files, adapting the tests from galera_3nodes for the current version of MariaDB. https://jira.mariadb.org/browse/MDEV-18426
| | * Merge 10.1 into 10.2Marko Mäkelä2018-12-171-0/+3
| | |\
| | | * MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-12-171-0/+3
| | | | | | | | | | | | | | | | Add check that file key management plugin is found.
* | | | MDEV-22181 : galera.galera_sst_mysqldump_with_key MTR failed: INSERT failed: ↵Jan Lindström2020-04-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 1146: Table 'test.t1' doesn't exist Add wait condition to make sure table test.t1 is replicated to node_2 before we insert to it.
* | | | MDEV-17048 Inconsistency voting support (#1373)Alexey Yurchenko2019-08-281-1/+8
|/ / / | | | | | | | | | | | | | | | * Collect and pass apply error data to provider * Rollback failed transaction and continue operation if provider returns SUCCESS * MTR tests for inconsistency voting
* | | MDEV-18565: Galera mtr-suite fails if galera library is not installedJulius Goryavsky2019-07-172-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, running mtr with an incorrect (for example, new or obsolete) version of wsrep_provider (for example, with the 26 version of libgalera_smm.so) leads to the failure of tests in several suites with vague error diagnostics. As for the galera_3nodes suite, the mtr also does not effectively check all the prerequisites after merge with MDEV-18426 fixes. For example, tests that using mariabackup do not check for presence of ss and socat/nc. This is due to improper handling of relative paths in mtr scripts. In addition, some tests in different suites can be run without setting the environment variables such as MTR_GALERA_TFMT, XBSTREAM, and so on. To eliminate all these issues, this patch makes the following changes: 1. Added auxiliary wsrep_mtr_check utility (which located in the mysql-test/lib/My/SafeProcess subdirectory), which compares the versions of the wsrep API that used by the server and by the wsrep provider library, and it does this comparison safely, without accessing the API if the versions do not match. 2. All checks related to the presence of mariabackup and utilities that necessary for its operation transferred from the local directories of different mtr suites (from the suite.pm files) to the main suite.pm file. This not only reduces the amount of code and eliminates duplication of identical code fragments, but also avoids problems due to the inability of mtr to consider relative paths to include files when checking skip combinations. 3. Setting the values of auxiliary environment variables that are necessary for Galera, SST scripts and mariabackup (to work properly) is moved to the main mysql-test-run.pl script, so as not to duplicate this code in different suites, and to avoid partial corrections of the same errors for different suites (while other suites remain uncorrected). 4. Fixed duplication of the have_file_key_management.inc and have_filekeymanagement.inc files between different suites, these checks are also transferred to the top level. 5. Added garbd presence check and garbd path variable. https://jira.mariadb.org/browse/MDEV-18565
* | | MDEV-18198 Fix MTR test galera_sr.galera_sr_table_contentsDaniele Sciascia2019-02-181-3/+3
| | | | | | | | | | | | | | | | | | * Created new binlog-header file * Fixed warning on SELECT INTO DUMPFILE * Re-recorded the test result
* | | Galera4Brave Galera Crew2019-01-239-19/+211
| | |
* | | MDEV-17771: Add Galera ist and sst tests using mariabackupJan Lindström2018-11-271-0/+3
| | | | | | | | | | | | Add check that file key management plugin is found.
* | | Merge 10.2 into 10.3Marko Mäkelä2018-11-261-4/+0
|/ / | | | | | | | | The test galera_sst_mariabackup_table_options was disabled, because the server refuses to start up due to wrong parameters.
* | Merge branch '10.1' into 10.2Sergei Golubchik2018-09-241-0/+11
|\ \ | |/
| * MDEV-15805: Test failure on galera.query_cacheJan Lindström2018-09-231-0/+11
| | | | | | | | | | Reset query cache after every test case and add wait after load infile.
* | Merge 10.1 into 10.2Marko Mäkelä2018-04-246-16/+14
|\ \ | |/
| * Merge pull request #713 from codership/MDEV-15948Jan Lindström2018-04-236-15/+14
| |\ | | | | | | MDEV-15948 Fix error "Lost connection to MySQL server..." in test gal…
| | * MDEV-15948 Followup commitDaniele Sciascia2018-04-234-4/+12
| | | | | | | | | | | | | | | | | | | | | * Increased timeout counter in galera_wait_ready.inc * Replaced useless include/wait_until_ready.inc after start_mysqld.inc in galera_st_*.inc with wait_condition on cluster size.
| | * MDEV-15948 Fix error "Lost connection to MySQL server..." in test ↵Daniele Sciascia2018-04-202-11/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | galera_sst_mysqldump Test galera_sst_mysqldump often fails with error "2013: Lost connection to MySQL server during query". The connection is lost after the test restart one of the nodes. This happens because the server closes client connections if it is joining a cluster through SST method mysqldump. On unlucky runs of the test it is possible that mysqld is restarted, and then mtr client is disconnected while it tries to determine if galera is ready before going on with the test. This patch rewrites galera_wait_ready.inc so that it is immune to being disconnected.
| * | MDEV-15929 Fix lock wait timeout on `SELECT @@GLOBAL.WSREP_ON`Daniele Sciascia2018-04-191-1/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes a lock wait timeout error on `SELECT @@GLOBAL.WSREP_ON` in `wait_wsrep_ready.inc`: ``` --connection node_2 ... --source include/kill_galera.inc --connection node_1 --source include/wait_until_connected_again.inc # This includes wait_wsrep_ready.inc ``` The problem is that on node_2, kill_galera.inc may return before the node is killed. So node_1 may still see that node_1 is alive and will attempt to sync wait when doing those `SELECT` statements. But sync wait is doomed to fail given that node_1 is killed, hence the lock wait timeout. One possible fix is to disable wsrep_sync_wait before including wait_until_connected_again. However, it appears that including wait_until_connected_again is not necessary at all in node_1, so this patch removes it altogether.
* | Merge branch '10.1' into 10.2Vicențiu Ciorbaru2018-04-101-1/+0
|\ \ | |/
| * MW-405 Remove wait_until_connected_again.inc from kill_galera.incDaniele Sciascia2018-04-031-1/+0
| | | | | | | | | | | | | | | | kill_galera.inc can no longer rely on wait_until_connected_again.inc. This is because wait_until_connected_again now tries to make sure that the server it is connected eventually transition to ready state. Whereas some tests may need to kill galera while the server is in a non-primary view.
* | Merge branch '10.1' into 10.2Sergei Golubchik2018-03-254-1/+15
|\ \ | |/
| * MDEV-15409 make sure every sst script is tested in buildbotSergei Golubchik2018-03-231-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | galera SST tests have a debug part, but we don't want to limit them to fulltest2 builder. So, add support for test files that have a debug part: * add maybe_debug.inc and maybe_debug.combinations * 'debug' combination is run when debug is available * 'release' combination is run otherwise * test wraps debug parts in if($with_debug) { ... } * and creates ,debug.rdiff for debug results
| * MDEV-15409 make sure every sst script is tested in buildbotSergei Golubchik2018-03-231-0/+4
| | | | | | | | create galera.galera_sst_mariabackup
| * MDEV-15409 make sure every sst script is tested in buildbotSergei Golubchik2018-03-231-0/+4
| | | | | | | | | | | | * make galera.galera_sst_xtrabackup* not big * auto-select between socat and nc, whatever available * auto-skip xtrabackup tests if no xtrabackup or neither socat nor nc
| * MDEV-15409 make sure every sst script is tested in buildbotSergei Golubchik2018-03-231-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fix galera.galera_sst_mysqldump test to work: * must connect to 127.0.0.1, where mysqld is listening * disable wsrep_sync_wait in wsrep_sst_mysqldump, otherwise sst can deadlock * allow 127.0.0.1 for bind_address and wsrep_sst_receive_address. (it's useful in tests, or when two nodes are on the same box, or when nodes are on different boxes, but the connection is tunelled, or whatever. Don't judge user's setup). MDEV-14070 * don't wait for client connections to die when doing mysqldump sst. they'll die in a due time, and if needed mysql will wait on locks until they do. MDEV-14069 Also don't mark it big, to make sure it's sufficiently tested
* | Merge branch '10.1' into 10.2Vicențiu Ciorbaru2018-03-211-0/+4
|\ \ | |/
| * MDEV-13549: Galera test failuresJan Lindström2018-03-191-0/+4
| | | | | | | | Fix test failure on galera_flush_local.
| * Merge branch '10.0-galera' into 10.1Sergei Golubchik2016-11-022-0/+14
| |\
| | * Fix/disable some failing galera tests.Nirbhay Choubey2016-11-012-0/+14
| | |
* | | MDEV-15540sjaakola2018-03-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The error log redirection for wsrep_recover run does not work in old version. For the wsrep_recovery run, error logging is supposed to go into: mysql-test/suite/galera/include/galera_wsrep_recover.inc In old version, this works only partially, 4 first lines of error messages after mysql startup do go into the galera_wsrep_recover.log, but after that the default error log file is enforced and remaining error logging goes into the default error log file. In this patch this problem is fixed by passing --log-error option in mysql startup This fix was tested with galera_gcache_recover test, which is currently in disabled state. Note that the test does not pass even after this fix, as there are further more issues in later test phases.
View Lorry Controller Status