Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: 5.5.33a-galera
-
Fix Version/s: 5.5.35-galera
-
Component/s: None
-
Labels:None
Description
I noticed that MariaDB Galera 5.5.33a starts with binlog_format=STATEMENT (when started with wsrep settings, that is as galera node).
As far as I know it is not supported by Galera.
Noticed for instance that deleting from an empty table gives an error:
MariaDB [test]> delete from my_table;
ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
Is it correct to start a galera node with binlog_format=ROW ?
Cheers
Claudio
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
As Galera requires ROW binlog-format to generate the writesets, MGC must be started
with --binlog-format=row in order to function normally.
As STATEMENT binlog format is not supported, closing it as "won't fix".
Could we at least add code to generate error message and then shutdown ?
Just tested 5.5.34 Galera,
now the [ERROR] message is in the log, but the instance starts anyway:
131219 18:28:01 [ERROR] WSREP: Only binlog_format = 'ROW' is currently supported. Configured value: 'STATEMENT'. Please adjust your configuration.
131219 18:28:03 mysqld_safe WSREP: Recovered position 699a1a64-68d2-11e3-820c-c29009febae0:0
131219 18:28:03 [ERROR] WSREP: Only binlog_format = 'ROW' is currently supported. Configured value: 'STATEMENT'. Please adjust your configuration.
131219 18:28:03 [Note] WSREP: wsrep_start_position var submitted: '699a1a64-68d2-11e3-820c-c29009febae0:0'
131219 18:28:03 [Note] WSREP: Read nil XID from storage engines, skipping position init
131219 18:28:03 [Note] WSREP: wsrep_load(): loading provider library '/PLAYGROUND/instances/galera/libgalera_smm.so'
131219 18:28:03 [Note] WSREP: wsrep_load(): Galera 2.6(r152) by Codership Oy <info@codership.com> loaded succesfully.
It starts:
MariaDB [test]> status;
--------------
bin/mysql Ver 15.1 Distrib 5.5.34-MariaDB, for Linux (x86_64) using readline 5.1
MariaDB [test]> create table pizza (id int, data varchar(100));
Query OK, 0 rows affected (0.20 sec)
MariaDB [test]> delete from pizza;
ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
Due to the STATEMENT format.