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

Replicate_Wild_Ignore_Table not working well

    XMLWordPrintable

Details

    Description

      I have a MySQL master server, lets call it MYSQL.
      Furthermore I have another server, which runs MariaDB. Let's call it MariaDB.

      MariaDB server acts as a slave. I have the following in /etc/my.cnf.d/server.cnf:

      replicate-wild-ignore-table = %.trades,%.cacheable,mysql.user

      I can confirm that SHOW SLAVE STATUS shows this:
      Replicate_Wild_Ignore_Table: %.trades,%.cacheable,mysql.user

      However, the slave MariaDB server replicates everything from MYSQL master, even the tables which it shouldn't. However, if I execute the following commands on MariaDB slave, it magically starts to work correctly (replicates only the tables not mentioned in wild ignore):

      STOP SLAVE;
      set global replicate_wild_ignore_table="%.trades,%.cacheable,mysql.user";
      START SLAVE;

      Again, show slave status still reports the same:
      Replicate_Wild_Ignore_Table: %.trades,%.cacheable,mysql.user

      I consider this a bug. It should ignore the tables in replication right from the start. By the way, if that matters, the mariadb slave is also configured to store statements in its binary log (as like it will be used as master some time later). Just a note. Attached is the content of file /etc/my.cnf.d/server.cnf (copy&pasted in windows, so probably with wrong CRLF newlines, ignore that)

      Attachments

        1. server.cnf
          1 kB
          Tomas Matejicek

        Activity

          People

            greenman Ian Gilfillan
            TomasM Tomas Matejicek
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.