[MXS-2776] Binlog filter skipping commit when writing to ColumnStore Created: 2019-11-22 Updated: 2019-12-02 Resolved: 2019-12-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | binlogrouter, Filter |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | 2.4.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Todd Stoffel (Inactive) | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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:
Result: No replication When replicating to an InnoDB table:
Result: Successful replication |
| Comments |
| Comment by Johan Wikman [ 2019-11-25 ] |
|
toddstoffel Please add your config as well. |
| Comment by markus makela [ 2019-12-02 ] |
|
Edit: The match parameter is only for the table and database names and thus would not work. |
| Comment by markus makela [ 2019-12-02 ] |
|
Turns out that an unwanted regex check was done on transaction management statements which would cause it to fail when the match parameter was used. |