summaryrefslogtreecommitdiff
path: root/mysql-test/suite/wsrep/t
Commit message (Collapse)AuthorAgeFilesLines
* MDEV-30318: galera error messages in mariadb log without galera enabledJulius Goryavsky2023-02-152-2/+14
| | | | | | | Post-fix to MDEV-30318 and MDEV-22570-related changes: unified handling of wsrep_provider by code so that "none" is interpreted as case-insensitive everywhere and that work with an empty string is supported everywhere.
* MDEV-30318 : galera error messages in mariadb log without galera enabledJan Lindström2023-02-145-0/+26
| | | | | | | | | Do not compile wsrep_provider plugin if WITH_WSREP is not enabled. We should not enable wsrep_provider plugin if WSREP_ON=OFF and at that case we can only print information that Plugin 'wsrep-provider' is disabled. Make sure tests require Galera library 26.4.14 if needed.
* MDEV-30120 Update the wsrep_provider_options read_only value in the ↵Jan Lindström2023-02-141-1/+6
| | | | | | | system_variables table. When wsrep-provider-options plugin is initialized we need to update wsrep-provider-options variable as READ_ONLY.
* MDEV-22570 Implement wsrep_provider_options as pluginDaniele Sciascia2023-02-146-0/+147
| | | | | | | | | | | | | | | | | | | | | - Provider options are read from the provider during startup, before plugins are initialized. - New wsrep_provider plugin for which sysvars are generated dynamically from options read from the provider. - The plugin is enabled by option plugin-wsrep-provider=ON. If enabled, wsrep_provider_options can no longer be used, (an error is raised on attempts to do so). - Each option is either string, integer, double or bool - Options can be dynamic / readonly - Options can be deprecated Limitations: - We do not check that the value of a provider option falls within a certain range. This type of validation is still done in Galera side. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* MDEV-27246 Implement a method to add IPs to allowlist for Galera Cluster ↵mkaruza2022-08-022-2/+2
| | | | | | node addresses that can make SST/IST requests Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* MDEV-28263: mariadb-tzinfo-to-sql improve wsrep and binlog casesDaniel Black2022-04-214-84/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The --skip-write-binlog message was confusing that it only had an effect if the galera was enabled. There are uses beyond galera so we apply SET SESSION SQL_LOG_BIN=0 as implied by the option without being conditional on the wsrep status. We also with --skip-write-binlog actually check the session @@WSREP_ON variable rather than the global server variable. Since 10.6, the wsrep_mode could replicate Aria and MyISAM, in which case no change to innodb and back is needed. By removing the conditions, we can use LOCK TABLES in a general case improving the load speed of Aria (MDEV-23326), regardless of the skip-write-binlog flag. The only case where we don't use LOCK TABLES is when we are replicating via Innodb, because wsrep_on=1 and wsrep_mode doesn't contain REPLICATE_ARIA{,MYISAM}. This uses an Innodb transaction instead. When replicating via InnoDB we change the table engine type back to what it was originally. By removing the \d and other syntax that requires parsing by the mariadb client, we can use the generated SQL more generally, like in the embedded server. We also save and restore the SQL_LOG_BIN and WSREP_ON session server variables so this can be included in the same session as other data without taking into changes in state. Remove wsrep.mysql_tzinfo_to_sql_symlink{,_skip} tests as they offered no additional coverage beyond main.mysql_tzinfo_to_sql_symlink (no server testing was done). Add galera.mariadb_tzinfo_to_sql to actually test the replication of tzinfo data through galera. The conditional executable comment around /*M!100602 ... START TRANSACTION .. LOCK TABLES.. */ is so that we can provide tzinfo files (MDEV-27113, MDBF-389) and in the case that a user uses it on a pre-10.6 server version it will still work. Both START TRANSACTION and LOCK TABLES are not supported in prepared statements in MariaDB versions earlier than 10.6.2. Reviewed by Brandon Nesterenko
* Update result files for Galera library 26.4.9Jan Lindström2021-07-272-2/+2
|
* MDEV-25591 : Test case cleanupsJan Lindström2021-05-042-34/+8
| | | | | | | | | | galera_var_wsrep_on_off : Add wait conditions to make sure DDL is replicated before continuing. wsrep.[variables|variables_debug] : Remove unnecessary parts and add check to correct number of variables or skip galera_ssl_reload: Add version check and SSL checks.
* Fix MTR test wsrep.variables_debugDaniele Sciascia2021-04-262-267/+23
| | | | | | | The test was changing variable wsrep_provider dynamically, but wsrep_provider was recently made read-only. followup for ce3a2a688db556d8
* More fixes to variable wsrep_onDaniele Sciascia2021-04-202-0/+48
| | | | | | | | | | | | | | * Disallow setting wsrep_on = 1 if wsrep_provider is unset. Also, move wsrep_on_basic from sys_vars to wsrep suite: this test now requires to run with wsrep_provider set * Disallow setting @@session.wsrep_on = 1 when @@global.wsrep_on = 0 * Handle the case where a new connection turns @@global.wsrep_on from off to on. In this case we would miss a call to wsrep_open, causing unexpected states in wsrep::client_state (causing assertions). * Disable wsrep.MDEV-22443 because it is no longer possible to enable wsrep_on, if server is started with wsrep_provider='none' Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* Merge branch '10.3' into 10.4Sergei Golubchik2021-02-231-3/+0
|\
| * Merge branch '10.2' into 10.3Sergei Golubchik2021-02-221-3/+0
| |\
| | * Merge branch 'bb-10.2-release' into 10.2Sergei Golubchik2021-02-221-27/+8
| | |\
| | * | MDEV-24867 : wsrep.variables MTR failed: Result length mismatchJan Lindström2021-02-171-4/+2
| | | | | | | | | | | | | | | | Stabilize test case.
* | | | Merge branch 'bb-10.3-release' into bb-10.4-releasemariadb-10.4.18Sergei Golubchik2021-02-191-25/+8
|\ \ \ \ | |/ / /
| * | | Merge branch 'bb-10.2-release' into bb-10.3-releasemariadb-10.3.28Sergei Golubchik2021-02-181-24/+8
| |\ \ \ | | | |/ | | |/|
| | * | make @@wsrep_provider and @@wsrep_notify_cmd read-onlymariadb-10.2.37Sergei Golubchik2021-02-181-26/+8
| | |/ | | | | | | | | | this should simplify run-time cluster management
| * | Merge remote-tracking branch 10.2 into 10.3Jan Lindström2020-11-031-8/+0
| |\ \ | | |/
| | * Clean up wsrep.variablesJan Lindström2020-11-031-6/+0
| | |
* | | MDEV-24596 : Assertion `state_ == s_exec || state_ == s_quitting' failed in ↵Jan Lindström2021-01-214-0/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wsrep::client_state::disable_streaming There were multiple problems here * wsrep_trx_fragment_size should not be set when wsrep is disabled or provider is not loaded * wsrep_trx_fragment_unit should not be set when wsrep is disabled or provider is not loaded * wsrep_debug has no effect if wsrep is disabled or provider is not loaded * wsrep_start_position should not be set when wsrep is disabled or provider is not loaded any other value than default * wsrep_start_position should be changed only when we are joiner or initialized * wsrep_start_position should be allowed to set only a value that exits, thus we need to add error handling to wsrep_sst_complete
* | | fixup 67cb7ea22ac1a510dcbaf9bc48f0f8cf9e0ce8f5Marko Mäkelä2020-11-031-3/+3
| | |
* | | Clean up wsrep.variablesJan Lindström2020-11-031-8/+0
| | |
* | | MDEV-22681 EXECUTE IMMEDIATE crashes server if wsrep is on.Teemu Ollakka2020-10-282-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A wsrep transaction was started for EXECUTE IMMEDIATE, which caused assertion failure when the executed statement was CREATE TABLE which should be executed in TOI mode. As a fix, don't start wsrep transaction for EXECUTE IMMEDIATE to let the wsrep state logic to be handled from inside stored procedure codepath. Reviewed-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | | After-merge fix to wsrep.variablesMarko Mäkelä2020-10-221-0/+1
| | | | | | | | | | | | We must make the test depend on a debug version of Galera.
* | | Merge 10.3 into 10.4Marko Mäkelä2020-10-225-2/+192
|\ \ \ | |/ /
| * | Merge 10.2 into 10.3Marko Mäkelä2020-10-222-1/+16
| |\ \ | | |/
| | * MDEV-17585 : wsrep.variables failed in buildbot with deadlock on CREATE USERJan Lindström2020-10-102-12/+24
| | | | | | | | | | | | | | | Stabilize test by using correct galera library and restore original galera cluster at end.
| * | Merge 10.2 into 10.3Marko Mäkelä2020-04-151-0/+1
| |\ \ | | |/
| | * MDEV-22021: Galera database could get inconsistent with rollback to savepointmkaruza2020-03-311-0/+1
| | | | | | | | | | | | | | | | | | When binlog is disabled, WSREP will not behave correctly when SAVEPOINT ROLLBACK is executed since we don't register handlers for such case. Fixed by registering WSREP handlerton for SAVEPOINT related commands.
* | | MDEV-23081 Stray XA transactions at startup, with wsrep_on=OFFDaniele Sciascia2020-10-213-0/+70
| | | | | | | | | | | | | | | | | | | | | Change xarecover_handlerton so that transaction with WSREP prefixed xids are rolled back when Galera is disabled. Reviewd-by: Jan Lindström <jan.lindstrom@mariadb.com>
* | | Fix MTR test wsrep.variablesDaniele Sciascia2020-09-281-0/+1
| | | | | | | | | | | | | | | Require galera_have_debug_sync.inc and re-record to include new variables exposed by latest galera library.
* | | MDEV-20581 Fix MTR test wsrep.variablesJan Lindström2020-09-141-3/+5
| | | | | | | | | | | | | | | Made the test work with --repeat option by adding galera_wait_ready.inc at the end of test. Recorded the test output.
* | | MDEV-23466 SIGABRT on SELECT WSREP_LAST_SEEN_GTIDDaniele Sciascia2020-08-192-0/+18
| | | | | | | | | | | | | | | SELECT WSREP_LAST_SEEN_GTID aborts the server if no provider is loaded.
* | | MDEV-23092 SIGABRT when setting invalid wsrep_providerDaniele Sciascia2020-08-192-0/+30
| | | | | | | | | | | | | | | | | | | | | Some invalid wsrep_provider paths may be interpreted as a valid directory. For example '/invalid/libgalera_smm.so' with UTF character set is interpreted as '/', which is a valid directory. A early check that wsrep_provider should not be a directory fixes it.
* | | MDEV-22443 wsrep::runtime_error on START TRANSACTIONDaniele Sciascia2020-08-192-0/+20
| | | | | | | | | | | | | | | | | | This happens with global wsrep_on disabled and local wsrep_on enabled. The fix consists in avoiding sync wait when global wsrep_on is disabled.
* | | MDEV-20625 : MariaDB asserting when enabling wsrep_onbb-10.4-MDEV-20625Jan Lindström2020-02-041-0/+1
| | | | | | | | | | | | | | | | | | | | | We need to release global system variables mutex before doing wsrep_init to avoid race with next show status and we need to save wsrep_on value as it is changed on wsrep_init. Added test case.
* | | MDEV-20625: MariaDB asserting when enabling wsrep=onJulius Goryavsky2020-02-042-0/+17
| | |
* | | Merge 10.3 into 10.4Marko Mäkelä2020-01-201-0/+1
|\ \ \ | |/ / | | | | | | | | | The MDEV-17062 fix in commit c4195305b2a8431f39a4c75cc1c66ba43685f7a0 was omitted.
| * | Merge branch '10.2' into 10.3Sergei Petrunia2020-01-171-1/+1
| |\ \ | | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Conflicts: # mysql-test/suite/galera/r/MW-388.result # mysql-test/suite/galera/t/MW-388.test # mysql-test/suite/innodb/r/truncate_inject.result # mysql-test/suite/innodb/t/truncate_inject.test # mysql-test/suite/rpl/r/rpl_stop_slave.result # mysql-test/suite/rpl/t/rpl_stop_slave.test # sql/sp_head.cc # sql/sp_head.h # sql/sql_lex.cc # sql/sql_yacc.yy # storage/xtradb/buf/buf0dblwr.cc
| | * MDEV-21498 : wsrep.binlog_format test failed on AzureJan Lindström2020-01-161-1/+1
| | | | | | | | | | | | Waiting wsrep_ready is possible only if wsrep_on=ON.
* | | Merge 10.3 into 10.4Marko Mäkelä2020-01-071-0/+4
|\ \ \ | |/ /
| * | Merge 10.2 into 10.3Marko Mäkelä2020-01-071-0/+4
| |\ \ | | |/
| | * MDEV-13569: wsrep_info.plugin failed in buildbot with "no nodes coming from ↵Jan Lindström2020-01-071-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | prim view Modify configuration so that all nodes are part of galera cluster i.e. wsrep_on=ON. Add missing wait conditions. test changes only.
| * | Merge 10.2 into 10.3Marko Mäkelä2019-12-278-3/+36
| |\ \ | | |/
| | * Merge 10.1 into 10.2Marko Mäkelä2019-12-234-0/+8
| | |\
| | | * MDEV-21209 : mysql_tzinfo_to_sql's Galera checks do not workJan Lindström2019-12-054-0/+8
| | | | | | | | | | | | | | | | | | | | wsrep_on parameter can be visible even when wsrep_on is set OFF so we need to check variable_value from I_S also.
| | * | MDEV-21335 : Galera test failure on suite wsrepJan Lindström2019-12-185-3/+28
| | | | | | | | | | | | | | | | Problem was that wsrep_on was OFF.
* | | | MDEV-21335 : Galera test failure on suite wsrepbb-10.4-MDEV-21335Jan Lindström2019-12-1814-16/+37
| | | | | | | | | | | | | | | | | | | | | | | | Problem was that wsrep_on was OFF. This is 10.4 version.
* | | | Merge branch '10.3' into 10.4Oleksandr Byelkin2019-12-091-0/+1
|\ \ \ \ | |/ / /
| * | | Merge remote-tracking branch 10.2 into 10.3Jan Lindström2019-12-021-1/+1
| |\ \ \ | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: mysql-test/suite/galera/t/galera_binlog_event_max_size_max-master.opt mysql-test/suite/innodb/r/innodb-mdev-7513.result mysql-test/suite/innodb/t/innodb-mdev-7513.test mysql-test/suite/wsrep/disabled.def storage/innobase/ibuf/ibuf0ibuf.cc
View Lorry Controller Status