Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-18557

Galera: Rolling upgrade: eliminate binlog format check for DDLs

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.4.3, 10.3.13
    • 10.4.3, 10.3.14
    • Galera
    • 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

      Attachments

        Activity

          People

            teemu.ollakka Teemu Ollakka
            shako Shahriyar Rzayev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.