Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2713

SET PASSWORD statement sent to all nodes, not only to master

    XMLWordPrintable

Details

    • MXS-SPRINT-92

    Description

      When a SET PASSWORD command is issued it is sent to all nodes, slaves included.
      This breaks replication if GTID is in use and gtid_strict_mode is ON.

      Here is an extract of the binlog generated by one of the slaves (log_slave_updates ON) that shows the same statement received twice, one from master (id 1) and one from the slave itself (id 3):

      # at 95169640
      #191003 7:59:27 server id 3 end_log_pos 95169682 CRC32 0x2dce3f19 GTID 1-3-612821036 ddl
      /*!100001 SET @@session.server_id=3*//*!*/;
      /*!100001 SET @@session.gtid_seq_no=612821036*//*!*/;
      # at 95169682
      #191003 7:59:27 server id 3 end_log_pos 95169830 CRC32 0x913f626e Query thread_id=9281131 exec_time=0 error_code=0
      SET TIMESTAMP=1570111167/*!*/;
      SET PASSWORD FOR 'user'@'10.0.0.1'='*C50EB75D7CB4C76B5264218B92BC69E6815B057A'
      /*!*/;
      # at 95169830
      #191003 7:59:27 server id 1 end_log_pos 95169872 CRC32 0x476ff7cf GTID 1-1-612821036 ddl
      /*!100001 SET @@session.server_id=1*//*!*/;
      /*!100001 SET @@session.gtid_seq_no=612821036*//*!*/;
      # at 95169872
      #191003 7:59:27 server id 1 end_log_pos 95170020 CRC32 0xb53e49f8 Query thread_id=83175357 exec_time=1126 error_code=0
      SET TIMESTAMP=1570111167/*!*/;
      SET PASSWORD FOR 'user'@'10.0.0.1'='*C50EB75D7CB4C76B5264218B92BC69E6815B057A'
      /*!*/;
      

      Attachments

        Activity

          People

            johan.wikman Johan Wikman
            rpizzi Rick Pizzi
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.