[MDEV-19563] Galera depends on deprecated option innodb_locks_unsafe_for_binlog Created: 2019-05-23  Updated: 2019-06-12  Resolved: 2019-06-12

Status: Closed
Project: MariaDB Server
Component/s: Galera, Storage Engine - InnoDB, Storage Engine - XtraDB
Affects Version/s: 10.0, 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.2.25, 10.1.41, 10.3.16, 10.4.6

Type: Bug Priority: Blocker
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: configuration

Issue Links:
Relates
relates to MDEV-18650 Options deprecated in previous versions Closed
relates to MDEV-19544 Remove innodb_locks_unsafe_for_binlog Closed

 Description   

The option innodb_locks_unsafe_for_binlog was deprecated already in MariaDB Server 10.0.0. Yet, Galera documentation recommends setting this option.

In MariaDB Server 10.5, MDEV-19544 will finally remove the deprecated option.

To provide a smoother upgrade path, I think that we should stop recommending or setting innodb_locks_unsafe_for_binlog=1 already in the 10.4 GA version, and if possible, in earlier versions as well.

If the correct operation of Galera currently depends on this setting, then we should extend the WSREP patches in InnoDB so that when Galera is use, the gap locks will continue to be skipped. I think that it would be a must to have these changes in 10.4, and it would be nice-to-have in earlier major versions.

 Comments   
Comment by Marko Mäkelä [ 2019-06-12 ]

seppo submitted a patch that removes the references to the deprecated option.

Generated at Thu Feb 08 08:52:39 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.