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

Binlog filter skipping commit when writing to ColumnStore

    XMLWordPrintable

    Details

    • Sprint:
      MXS-SPRINT-95

      Description

      I am using the Binlog Router to replicate InnoDB and ColumnStore data. Both work as expected unless the binlog filter is introduced into the configuration. At this point the ColumnStore replication stops committing to the target table. You'll notice that only when replicating to the ColumnStore table does the binglogfilter add a second line about COMMIT. This does not happen when the target is InnoDB table.

      MaxScale logging shows the following:

      When replicating to a ColumnsStore table:

      2019-11-21 19:18:47   info   : (8) [binlogfilter] [    ] (columnstore) INSERT INTO `columnstore`.`customers` SET `c` = 'Monty'
      2019-11-21 19:18:47   info   : (8) [binlogfilter] [SKIP] (columnstore) COMMIT
      

      Result: No replication

      When replicating to an InnoDB table:

      2019-11-21 19:22:13   info   : (11) [binlogfilter] [    ] (innodb) INSERT INTO `innodb`.`customers` SET `c` = 'Monty'
      

      Result: Successful replication

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            toddstoffel Todd Stoffel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration