summaryrefslogtreecommitdiff
path: root/mysql-test/suite/galera_3nodes
Commit message (Collapse)AuthorAgeFilesLines
* Fixed dependency checking in some Galera testsJulius Goryavsky2019-07-182-0/+2
|
* MDEV-18565: Galera mtr-suite fails if galera library is not installedJulius Goryavsky2019-07-175-52/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-16021: galera mtr test galera_evs_suspect_timeout crashedJan Lindström2019-05-172-25/+48
| | | | | Crash was timeout crash. Add correct waits for connections, wsrep sync waits and auto increment offset save and restore.
* MDEV-17262: mysql crashed on galera while node rejoined cluster (#895)sysprg2019-03-183-0/+164
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch contains a fix for the MDEV-17262/17243 issues and new mtr test. These issues (MDEV-17262/17243) have two reasons: 1) After an intermediate commit, a transaction loses its status of "transaction that registered in the MySQL for 2pc coordinator" (in the InnoDB) due to the fact that since version 10.2 the write_row() function (which located in the ha_innodb.cc) does not call trx_register_for_2pc(m_prebuilt->trx) during the processing of split transactions. It is necessary to restore this call inside the write_row() when an intermediate commit was made (for a split transaction). Similarly, we need to set the flag of the started transaction (m_prebuilt->sql_stat_start) after intermediate commit. The table->file->extra(HA_EXTRA_FAKE_START_STMT) called from the wsrep_load_data_split() function (which located in sql_load.cc) will also do this, but it will be too late. As a result, the call to the wsrep_append_keys() function from the InnoDB engine may be lost or function may be called with invalid transaction identifier. 2) If a transaction with the LOAD DATA statement is divided into logical mini-transactions (of the 10K rows) and binlog is rotated, then in rare cases due to the wsrep handler re-registration at the boundary of the split, the last portion of data may be lost. Since splitting of the LOAD DATA into mini-transactions is technical, I believe that we should not allow these mini-transactions to fall into separate binlogs. Therefore, it is necessary to prohibit the rotation of binlog in the middle of processing LOAD DATA statement. https://jira.mariadb.org/browse/MDEV-17262 and https://jira.mariadb.org/browse/MDEV-17243
* Merge 10.1 into 10.2Marko Mäkelä2019-03-118-0/+205
|\
| * Galera 3 versions of the result files recorded.Jan Lindström2019-03-093-15/+29
| |
| * galera: test cases for non [mysqld] section for configurationDaniel Black2019-03-097-0/+191
| |
* | Merge 10.1 into 10.2Marko Mäkelä2019-02-122-0/+2
|\ \ | |/
| * MDEV-18426: Most of the mtr tests in the galera_3nodes suite failJulius Goryavsky2019-02-1215-30/+102
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most of the mtr tests in the galera_3nodes suite fail for a variety of reasons with a variety of errors. This patch 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. This patch also synchronizes some galera_3nodes-related files with the latest changes made for MDEV-17835 (v2 patch) and for MDEV-18379 in other branches (10.2 and 10.3). Closes #1161
* | MDEV-18426: Most of the mtr tests in the galera_3nodes suite failJulius Goryavsky2019-02-0612-27/+100
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Some more fixes for --suite=galera_3nodesMarko Mäkelä2019-02-025-1/+53
| |
* | MDEV-18379: IPv6 compatibility changes/Unification of check for IPv6Julius Goryavsky2019-02-0212-9/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch contains the port of the MDEV-18379 patch for 10.2 branch, but also includes a number of changes made within MDEV-17835, which are necessary for the normal operation of tests that use IPv6: 1) Currently, the three-node mtr suite for Galera (galera_3nodes) uses a separate IPv6 availability check using the "have_ipv6.inc" file. This check duplicates a more accurate check at suite.pm level, which can be used by including the file "check_ipv6.inc". This patch removes this discrepancy between suites. 2) Fixed numerous bugs in the SST scripts and in the mtr test files (galera_3nodes mtr suite) that prevented the use of Galera with IPv6 addresses. 3) Fixed flaws in the galera_3nodes mtr suite control scripts, because of which they could not work with mariabackup. 4) Fixed flaws in the rsync and mysqldump tests (for galera_3nodes mtr tests suite). These tests were not performed successfully without these fixes. 5) GAL-501 test in the galera_3nodes suite does not contain the option "--bind-address=::" that is needed for the test to work correctly with IPv6 (at least on some systems), since without it the server will not wait for connections on the IPv6 interface. https://jira.mariadb.org/browse/MDEV-18379 and partially https://jira.mariadb.org/browse/MDEV-17835
* | Merge 10.1 into 10.2Marko Mäkelä2019-02-0220-57/+255
|\ \ | |/
| * MDEV-18379: Unification of check for IPv6Julius Goryavsky2019-01-2621-58/+255
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch contains the port of the MDEV-18379 patch for 10.1 branch, but also includes a number of changes made within MDEV-17835, which are necessary for the normal operation of tests that use IPv6: 1) Fixed flaws in the galera_3nodes mtr suite control scripts, because of which they could not work with mariabackup. 2) Fixed numerous bugs in the SST scripts and in the mtr test files (galera_3nodes mtr suite) that prevented the use of Galera with IPv6 addresses. 3) Fixed flaws in tests for rsync and mysqldump (for galera_3nodes mtr tests suite). These tests were not performed successfully without these fixes. 4) Currently, the three-node mtr suite for Galera (galera_3nodes) uses a separate IPv6 availability check using the "have_ipv6.inc" file. This check duplicates a more accurate check at suite.pm level, which can be used by including the file "check_ipv6.inc". This patch removes this discrepancy between suites. 5) GAL-501 test in the galera_3nodes suite does not contain the option "--bind-address=::" which is needed for the test to work correctly with IPv6 (at least on some systems), since without it the server will not wait for connections on the IPv6 interface. https://jira.mariadb.org/browse/MDEV-18379 and partially https://jira.mariadb.org/browse/MDEV-17835
* | MDEV-15522: Change galera suite MTR tests to use mariabackup instead of ↵Jan Lindström2018-11-221-1/+2
| | | | | | | | | | | | xtrabackup Disable galera_3nodes tests using xtrabackup.
* | Merge branch '10.1' into 10.2Oleksandr Byelkin2018-09-142-28/+58
|\ \ | |/
| * Merge branch '10.0-galera' into 10.1Sergei Golubchik2018-09-072-28/+58
| |\
| | * 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.
* | | MDEV-16052 galera mtr galera_certification_double_failure fails with deadlockmkaruza2018-09-111-1/+1
| | | | | | | | | | | | There was change in error reporting from my_error to my_message so new recording is required.
* | | Merge branch '10.1' into 10.2Sergei Golubchik2018-06-212-0/+2
|\ \ \ | |/ /
| * | Merge branch '10.0-galera' into 10.1Vicențiu Ciorbaru2018-06-122-0/+2
| |\ \ | | |/
| | * Galera MTR Tests: missing wsrep_sync_wait in test galera_evs_suspect_timeoutDaniele Sciascia2018-05-082-0/+2
| | |
* | | Merge branch '10.1' into 10.2Vicențiu Ciorbaru2018-04-101-5/+0
|\ \ \ | |/ /
| * | MW-405 Adjust galera_pc_weight to new wait_until_connected_againDaniele Sciascia2018-04-031-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | Test galera_3nodes.galera_pc_weight started to fail because it expects to use wait_until_connected_again while remaining in non-primary view. Hopefully this is the only test which makes this assumption, and fortunately those wait_until_connected_again seem unnecessary, so this patch removes them.
* | | Merge branch 'github/10.1' into 10.2Sergei Golubchik2018-02-063-2/+17
|\ \ \ | |/ /
| * | Merge branch 'github/10.0-galera' into 10.1Sergei Golubchik2018-02-033-2/+17
| |\ \ | | |/
| | * mtr: minor (and incomplete) fixes for suite galera_3nodeDaniel Black2018-01-144-2/+20
| | |
* | | Merge remote-tracking branch 'origin/10.1' into bb-10.2-vicentiuVicențiu Ciorbaru2017-12-284-0/+673
|\ \ \ | |/ /
| * | MDEV-10715 Galera: Replicate MariaDB GTID to other nodes in the clusterSachin Setiya2017-12-254-0/+673
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem:- Gtid are not transferred in Galera Cluster. Solution:- We need to transfer gtid in the case on either when cluster is slave/master in async replication. In normal Gtid replication gtid are generated on recieving node itself and it is always on sync with other nodes. Because galera keeps node in sync , So all nodes get same no of event groups. So the issue arises when say galera is slave in async replication. A | (Async replication) D <-> E <-> F {Galera replication} So what should happen is that all node should apply the master gtid but this does node happen, becuase node E, F does not recieve gtid from D in write set , So what E(or F) does is that it applies wsrep_gtid_domain_id, D server-id , E gtid next seq no. This generated gtid does not always work when say A has different domain id. So In this commit, on galera node when we see that this event is recieved from master we simply write Gtid_Log_Event in write_set and send it to other nodes.
* | | Merge branch '10.1' into 10.2Sergei Golubchik2017-10-241-0/+3
|\ \ \ | |/ /
| * | Bug FixSachin Setiya2017-10-111-0/+3
| | | | | | | | | | | | | | | Tests in galera_3nodes fails to start because galera_port , sst_port is not defined.
* | | Merge 10.1 into 10.2Marko Mäkelä2017-08-3116-7/+518
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For running the Galera tests, the variable my_disable_leak_check was set to true in order to avoid assertions due to memory leaks at shutdown. Some adjustments due to MDEV-13625 (merge InnoDB tests from MySQL 5.6) were performed. The most notable behaviour changes from 10.0 and 10.1 are the following: * innodb.innodb-table-online: adjustments for the DROP COLUMN behaviour change (MDEV-11114, MDEV-13613) * innodb.innodb-index-online-fk: the removal of a (1,NULL) record from the result; originally removed in MySQL 5.7 in the Oracle Bug #16244691 fix https://github.com/mysql/mysql-server/commit/377774689bf6a16af74182753fe950d514c2c6dd * innodb.create-index-debug: disabled due to MDEV-13680 (the MySQL Bug #77497 fix was not merged from 5.6 to 5.7.10) * innodb.innodb-alter-autoinc: MariaDB 10.2 behaves like MySQL 5.6/5.7, while MariaDB 10.0 and 10.1 assign different values when auto_increment_increment or auto_increment_offset are used. Also MySQL 5.6/5.7 exhibit different behaviour between LGORITHM=INPLACE and ALGORITHM=COPY, so something needs to be tested and fixed in both MariaDB 10.0 and 10.2. * innodb.innodb-wl5980-alter: disabled because it would trigger an InnoDB assertion failure (MDEV-13668 may need additional effort in 10.2)
| * | Merge remote-tracking branch 'origin/10.0-galera' into 10.1Jan Lindström2017-08-2116-7/+518
| |\ \ | | |/
| | * Galera test fixes and add remaining test failures as disabled.Jan Lindström2017-08-181-6/+1
| | |
| | * Galera MTR Tests: Test case for GAL-501 Improved URI parsing for IPv6 addressesPhilip Stoev2017-08-143-0/+78
| | |
| | * MW-86 Adjust MTR tests for changes to wsrep_sync_waitDaniele Sciascia2017-08-143-1/+161
| | |
| | * Galera MTR Tests: Tests for MW-366 - improved support for IPv6Philip Stoev2017-08-149-0/+278
| | |
* | | Merge 10.1 into 10.2Marko Mäkelä2017-06-082-5/+5
|\ \ \ | |/ / | | | | | | Replace have_innodb_zip.inc with innodb_page_size_small.inc.
| * | Merge branch '10.0-galera' into 10.1Sergei Golubchik2017-05-262-5/+5
| |\ \ | | |/
| | * Galera MTR Tests: MW-308 , MW-307, GCF-992Sachin Setiya2017-03-121-7/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * a dedicated test for wsrep_retry_autocommit * some galera_toi_* tests were only passing because wsrep_retry_autocommit was in effect. The tests were changed to do not use autocommit * higher timeout values in galera_2nodes.cnf , galera_3nodes.cnf # Conflicts: # mysql-test/suite/galera/galera_2nodes.cnf # mysql-test/suite/galera/r/galera_defaults.result # mysql-test/suite/galera_3nodes/galera_3nodes.cnf
| | * Galera MTR Tests: Test for GCF-942 - safe_to_bootstrap flag in grastate.datPhilip Stoev2017-03-123-0/+191
| | |
| | * MDEV-11490 Galera_3nodes test suite does not suppress Warnings.Sachin Setiya2016-12-211-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | Problem:- While running individual tests of Galera_3nodes , We get warnings like '[Warning] WSREP: Could not open state file for reading: '. And because of this individual tests fails. Solution:- We change suite.pm of Galera_3nodes to supress these warnings.
* | | Merge 10.1 into 10.2Marko Mäkelä2017-04-283-2/+195
|\ \ \ | |/ /
| * | Galera MTR Tests: MW-308 , MW-307, GCF-992Sachin Setiya2017-04-061-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | * a dedicated test for wsrep_retry_autocommit * some galera_toi_* tests were only passing because wsrep_retry_autocommit was in effect. The tests were changed to do not use autocommit * higher timeout values in galera_2nodes.cnf , galera_3nodes.cnf Signed-off-by: Sachin Setiya <sachin.setiya@mariadb.com>
| * | Galera MTR Tests: Test for GCF-942 - safe_to_bootstrap flag in grastate.datPhilip Stoev2017-04-062-0/+189
| | |
* | | Merge 10.1 into 10.2Marko Mäkelä2016-12-301-1/+3
|\ \ \ | |/ /
| * | MDEV-11490 Galera_3nodes test suite does not suppress Warnings.Sachin Setiya2016-12-211-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | Problem:- While running individual tests of Galera_3nodes , We get warnings like '[Warning] WSREP: Could not open state file for reading: '. And because of this individual tests fails. Solution:- We change suite.pm of Galera_3nodes to supress these warnings.
| * | Merge branch '10.0-galera' into 10.1Sergei Golubchik2016-11-021-0/+2
| |\ \ | | |/
| | * Fix/disable some failing galera tests.Nirbhay Choubey2016-11-011-0/+2
| | |
* | | Fix failing galera tests.Nirbhay Choubey2016-12-192-0/+29
| | |
View Lorry Controller Status