[MDEV-18557] Galera: Rolling upgrade: eliminate binlog format check for DDLs Created: 2019-02-12  Updated: 2019-02-21  Resolved: 2019-02-21

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.4.3, 10.3.13
Fix Version/s: 10.4.3, 10.3.14

Type: Bug Priority: Major
Reporter: Shahriyar Rzayev (Inactive) Assignee: Teemu Ollakka
Resolution: Fixed Votes: 0
Labels: galera
Environment:

Ubuntu 18.04


 Description   

Found this during upgrade tests:

  • Start given number of nodes - with my test 5 nodes with 10.3 Maria + 3.x Galera.
  • Shutdown node5
  • Start node5 with 10.4 Maria + 4.x Galera.(upgrade)
  • Run mysql_upgrade on node5
  • Shutdown node5
  • Start node5
  • Run followings:

MariaDB [(none)]> set session wsrep_trx_fragment_size=2147483647;
 
Query OK, 0 rows affected (0.000 sec)
 
 
 
MariaDB [(none)]> select @@wsrep_trx_fragment_size;
 
+---------------------------+
 
| @@wsrep_trx_fragment_size |
 
+---------------------------+
 
|                2147483647 |
 
+---------------------------+
 
1 row in set (0.002 sec)
 
 
 
MariaDB [(none)]> drop database sbtest;
 
ERROR 1235 (42000): Streaming replication not supported with binlog_format=STATEMENT
 
MariaDB [(none)]> select @@binlog_format;
 
+-----------------+
 
| @@binlog_format |
 
+-----------------+
 
| ROW             |
 
+-----------------+
 
1 row in set (0.002 sec)

As discussed with Teemu:

DROP DATABASE is replicated as Query_log_event, which is the format for STATEMENT replication. I guess the binlog format check should not care about DDLs

 Comments   
Comment by Shahriyar Rzayev (Inactive) [ 2019-02-21 ]

Can be closed as related PR is merged in 10.4

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