[MCOL-3556] Switch to per-UM setting for replication slave Created: 2019-10-14 Updated: 2019-11-06 Resolved: 2019-11-06 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Andrew Hutchings (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2019-06 |
| Description |
|
ColumnStore needs to set whether an individual UM should replay slave events on a ColumnStore table. This will be done with a new MariaDB variable called "columnstore_replication_slave" which is off by default and can only be changed in my.cnf, not at runtime. It cannot be changed at runtime because it would be a global variable that would need to be re-read, which requires the replication thread to end and restart. This overly complicates things and therefore a MariaDB restart is easier. |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2019-10-18 ] |
|
For QA: To enable ColumnStore to replicate events from another engine you need to set columnstore_replication_slave=on in one of the my.cnf files (such as columnstore.cnf) instead of setting the XML setting as per 1.2. The XML setting is now ignored. |
| Comment by Daniel Lee (Inactive) [ 2019-11-04 ] |
|
Build tested: 1.4.1-1 engine commit: Test replication between two columnstore installations. On the slave, columnstore_replication_slave can be inserted in the server.cnf or columnstore.cnf. Columnstore engine and Innodb engine tables are replicated as it. Is this the expected behavior? or is the innodb table should also be replicated as columnstore table? |
| Comment by Andrew Hutchings (Inactive) [ 2019-11-06 ] |
|
That is expected behaviour, we haven't done any magic to MariaDB server to change table type on the fly (although there are ways of doing that) |