mariadb/wsrep_on_without_provider.test at ead61d9bd96b773a3bbacf16c20df7cc34d85c96 - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-07-21 21:22:27 +03:00

Files

Daniele Sciascia eb4123eefc More fixes to variable wsrep_on

* 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>

2021-04-20 08:24:14 +03:00

9 lines

182 B

Plaintext

Raw Blame History

 --source include/not_embedded.inc
 #
 # @@global.wsrep_on is not allowed if there
 # is no wsrep_provider
 #
 --error ER_WRONG_ARGUMENTS
 SET GLOBAL wsrep_on=ON;
 SELECT @@global.wsrep_on;