summaryrefslogtreecommitdiff
path: root/sql/wsrep_var.h
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '10.1' into 10.2Vicențiu Ciorbaru2018-03-211-0/+1
|\
| * refs MW-245 - merged wsrep_dirty_reads and wsrep_reject_queries from PXCsjaakola2018-03-201-0/+1
| |
| * MDEV-12837: WSREP: BF lock wait longJan Lindström2017-12-091-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is 10.1 version where no merge error exists. wsrep_on_check New check function. Galera can't be enabled if innodb-lock-schedule-algorithm=VATS. innobase_kill_query In Galera async kill we could own lock mutex. innobase_init If Variance-Aware-Transaction-Sheduling Algorithm (VATS) is used on Galera we refuse to start InnoDB. Changed innodb-lock-schedule-algorithm as read-only parameter as it was designed to be. lock_rec_other_has_expl_req, lock_rec_other_has_conflicting, lock_rec_lock_slow lock_table_other_has_incompatible lock_rec_insert_check_and_lock Change pointer to conflicting lock to normal pointer as this pointer contents could be changed later.
* | MDEV-12837: WSREP: BF lock wait longJan Lindström2017-12-071-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem was a merge error from MySQL wsrep i.e. Galera. wsrep_on_check New check function. Galera can't be enabled if innodb-lock-schedule-algorithm=VATS. innobase_kill_query In Galera async kill we could own lock mutex. innobase_init If Variance-Aware-Transaction-Sheduling Algorithm (VATS) is used on Galera we fall back to First-Come-First-Served (FCFS) with notice to user. Changed innodb-lock-schedule-algorithm as read-only parameter as it was designed to be. lock_reset_lock_and_trx_wait Use ib::hex() to print out transaction ID. lock_rec_other_has_expl_req, lock_rec_other_has_conflicting, RecLock::add_to_waitq lock_rec_lock_slow lock_table_other_has_incompatible lock_rec_insert_check_and_lock lock_prdt_other_has_conflicting Change pointer to conflicting lock to normal pointer as this pointer contents could be changed later. RecLock::create Conclicting lock pointer is moved to last parameter with default value NULL. This conflicting transaction could be selected as victim in Galera if requesting transaction is BF (brute force) transaction. In this case contents of conflicting lock pointer will be changed. Use ib::hex() to print transaction ids.
* | Merge 10.1 into 10.2Marko Mäkelä2017-08-311-3/+1
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-211-3/+1
| |\
* | \ Merge branch '10.1' into 10.2Sergei Golubchik2016-09-091-0/+3
|\ \ \ | |/ /
| * | Post merge fixes.Nirbhay Choubey2016-08-251-0/+2
| | |
| * | Merge branch '10.0-galera' into bb-10.1-sergNirbhay Choubey2016-08-251-0/+1
| |\ \ | | |/
| | * MW-267 Enforce wsrep_max_ws_size limit in wsrep providerDaniele Sciascia2016-07-251-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changes variable wsrep_max_ws_size so that its value is linked to the value of provider option repl.max_ws_size. That is, changing the value of variable wsrep_max_ws_size will change the value of provider option repl.max_ws_size, and viceversa. The writeset size limit is always enforced in the provider, regardless of which option is used.
| | * bzr merge -c4123 codership/5.6/Nirbhay Choubey2014-08-121-1/+2
| | | | | | | | | | | | | | | (minus http://bazaar.launchpad.net/~codership/codership-mysql/5.6/revision/4122)
| | * Local merge of patch for MDEV-4647 from maria-5.5-galera.Nirbhay Choubey2014-07-221-1/+3
| | |
| | * bzr merge -r3895..3903 lp:codership-mysql/5.5 Seppo Jaakola2013-11-261-0/+2
| | | | | | | | | | | | | | | This is just before 5.5.34 merge in wsrep-5.5 branch
| | * bzr merge -r3890..3891 lp:codership-mysql/5.5Seppo Jaakola2013-11-061-0/+81
| |
* | MDEV-10492: Assertion failure on shutdown when wsrep_sst_auth set in configNirbhay Choubey2016-08-031-2/+0
| | | | | | | | | | | | | | The memory alloc-ed initially for wsrep_sst_auth to store the value specified in config was lost as the global variable was reset while in process of masking it and thus, could never be reclaimed on shutdown.
* | MDEV-6368: assertion xid_seqno > trx_sys_cur_xid_seqnoNirbhay Choubey2016-05-311-1/+1
|/ | | | | | | | | - Validate the specified wsrep_start_position value by also checking the return status of wsrep->sst_received. This also ensures that changes in wsrep_start_position is not allowed when the node is not in JOINING state. - Do not allow decrease in seqno within same UUID. - The initial checkpoint in SEs should be [0...:-1].
* Improve performance for calculating memory allocationMonty2015-02-011-0/+3
| | | | Extend interface for 'show variables' with current scope
* fixing embedded: first set of changes (storage engines don't work yet)Sergei Golubchik2014-10-011-1/+1
|
* cleanup: galera merge, simple changesSergei Golubchik2014-10-011-2/+17
|
* MDEV-6247: Merge 10.0-galera to 10.1.Jan Lindström2014-08-261-0/+86
Merged lp:maria/maria-10.0-galera up to revision 3879. Added a new functions to handler API to forcefully abort_transaction, producing fake_trx_id, get_checkpoint and set_checkpoint for XA. These were added for future possiblity to add more storage engines that could use galera replication.
View Lorry Controller Status