[MCOL-1217] newly added user module didnt have mysql replication slave setup Created: 2018-02-16 Updated: 2018-04-17 Resolved: 2018-04-17 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.1.3 |
| Fix Version/s: | 1.1.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hill (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
amazon ami 1.1.3 |
||
| Sprint: | 2018-04, 2018-05, 2018-06, 2018-07, 2018-08 |
| Description |
|
started with 1um/2pm system ami created, added um2 succesfully. check for mysql rep slave and it was setup. MariaDB [(none)]> show slave status\G; ERROR: No query specified MariaDB [(none)]> exit |
| Comments |
| Comment by David Hill (Inactive) [ 2018-02-16 ] |
|
problem is because we removed the mysql rep setup after the startsystem, which now causes this issue. need to investigate further |
| Comment by David Hill (Inactive) [ 2018-02-17 ] |
|
work around fix.. after module has been added, enabled started. run the following command to get the MariaDB/MySQL Replication setup on it. mcsadmin enableMySQLReplication |
| Comment by David Hill (Inactive) [ 2018-03-15 ] |
|
fixed.. code changes 1. ProcMgr addModule at the end: |
| Comment by David Hill (Inactive) [ 2018-03-15 ] |
|
https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/429 |
| Comment by David Hill (Inactive) [ 2018-03-15 ] |
|
To test... Addmodule 0n a um or local query pm. Check mysql rep slave setup on new module |
| Comment by Daniel Lee (Inactive) [ 2018-04-17 ] |
|
Reproduced the issue in 1.1.3-1 |
| Comment by Daniel Lee (Inactive) [ 2018-04-17 ] |
|
Build verified: 1.1.4-1 ami (ami-66036f1e, US-west) Verified that replication slave started after adding um2 and enabling the it. MariaDB [(none)]> show slave status\G;
|