mariadb/rpl_start_stop_slave-slave.opt at 730fb2881fda901b9ff4a008e547458545ae37bd - mariadb - GitFox

database/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-08-26 01:44:06 +03:00

Files

Andrei Elkin badc6a127d Bug#38205 Row-based Replication (RBR) causes inconsistencies: HA_ERR_FOUND_DUP

Bug#319  if while a non-transactional slave is replicating a transaction possible problem 

It is impossible to roll back a mixed engines transaction when one of the engine is
non-transaction. In replication that fact is crucial because the slave can not safely
re-apply a transction that was interrupted with STOP SLAVE.

Fixed with making STOP SLAVE not be effective immediately in the case the current
group of replication events has modified a non-transaction table. In order for slave to leave
either the group needs finishing or the user issues KILL QUERY|CONNECTION slave_thread_id.

2009-03-26 10:25:06 +02:00

2 lines

30 B

Plaintext

Raw Blame History

--innodb_lock_wait_timeout=60