summaryrefslogtreecommitdiff
path: root/mysql-test/suite/galera_3nodes
Commit message (Collapse)AuthorAgeFilesLines
...
| | | * Galera MTR Tests: missing wsrep_sync_wait in test galera_evs_suspect_timeoutDaniele Sciascia2018-05-082-0/+2
| | | |
* | | | Merge remote-tracking branch '10.2' into 10.3Vicențiu Ciorbaru2018-04-121-5/+0
|\ \ \ \ | |/ / /
| * | | 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 bb-10.2-ext into 10.3Marko Mäkelä2018-02-153-2/+17
|\ \ \ \ | |/ / /
| * | | 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 bb-10.2-ext into 10.3Marko Mäkelä2018-01-044-0/+673
|\ \ \ \ | |/ / /
| * | | 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.
* | | | Test cleanup related to MDEV-12501Vesa Pentti2017-12-161-1/+0
| | | | | | | | | | | | | | | | * Removing unnecessary --plugin-maturity=unknown definitions from tests
* | | | MDEV-12501 -- set --maturity-level by defaultVesa Pentti2017-12-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Note: breaking change; since this commit, a plugin that has worked so far might get rejected due to plugin maturity * mariabackup is not affected (allows all plugins) * VERSION file defines SERVER_MATURITY, which defines the corresponding numeric value as SERVER_MATURITY_LEVEL in include/mysql_version.h * The default value for 'plugin_maturity' is SERVER_MATURITY_LEVEL - 1 * Logs a warning if a plugin has maturity lower than SERVER_MATURITY_LEVEL * Tests suppress the plugin maturity warning * Tests use --plugin-maturity=unknown by default so as not to fail due to the stricter plugin maturity handling
* | | | Search for galera libraries also in /usr/lib64/galera-3Monty2017-12-081-2/+4
| | | | | | | | | | | | | | | | This is where Codership's offical rpm's puts them
* | | | Revert "MDEV-12501 -- set --maturity-level by default"Vesa Pentti2017-12-051-1/+0
| | | | | | | | | | | | | | | | This reverts commit 1af2d7ba235305ffd4c24a47cccafd5fe6815d9e.
* | | | MDEV-12501 -- set --maturity-level by defaultVesa Pentti2017-12-041-0/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Note: breaking change; since this commit, a plugin that has worked so far might get rejected due to plugin maturity * mariabackup is not affected (allows all plugins) * VERSION file defines SERVER_MATURITY, which defines the corresponding numeric value as SERVER_MATURITY_LEVEL in include/mysql_version.h * The default value for 'plugin_maturity' is SERVER_MATURITY_LEVEL - 1 * Logs a warning if a plugin has maturity lower than SERVER_MATURITY_LEVEL * Tests suppress the plugin maturity warning * Tests use --plugin-maturity=unknown by default so as not to fail due to the stricter plugin maturity handling
* | | 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
| | |
* | | Fix/disable some failing galera tests.Nirbhay Choubey2016-11-071-0/+2
| | |
* | | Update test results in galera, galera_3nodes suites.Nirbhay Choubey2016-11-073-0/+21
|/ /
* | Merge branch '10.0-galera' into bb-10.1-sergNirbhay Choubey2016-08-2510-25/+35
|\ \ | |/
| * Fixes/improvements in galera test suiteNirbhay Choubey2016-08-241-14/+7
| |
| * Fixes for failing tests (post-merge).Nirbhay Choubey2016-08-211-0/+2
| |
| * Galera MTR Tests: increase timeouts and adjust some sporadically-failing ↵Philip Stoev2016-08-215-8/+13
| | | | | | | | tests so that the Galera suites can be run with --parallel=4
| * Galera MTR Tests: Run galera_pc_weight on freshly started servers in order ↵Philip Stoev2016-08-211-0/+5
| | | | | | | | to prevent interaction with other tests
| * Galera MTR Tests: force galera_3nodes.galera_pc_bootstrap.test to run on a ↵Philip Stoev2016-08-211-0/+5
| | | | | | | | fresh cluster in order to avoid interaction with galera_3nodes.galera_innobackupex_backup.test
| * Galera MTR Tests: Adjust tests for xtrabackup 2.4.2Philip Stoev2016-08-211-3/+3
| |
* | Merge branch '10.0-galera' into bb-10.1-sergNirbhay Choubey2016-02-242-4/+5
|\ \ | |/
| * Helpers to deal with galera dbug sync points.Teemu Ollakka2016-02-222-4/+5
| |
* | Merge branch 'github/10.0-galera' into 10.1Sergei Golubchik2015-11-1916-5/+366
|\ \ | |/
| * Fix failing test casesNirbhay Choubey2015-09-143-3/+4
| | | | | | | | | | * Also modified name regex to include '#' as a valid symbol for tests under disabled.def.
View Lorry Controller Status