[MCOL-938] columnstore replication failover from master updates server-id Created: 2017-09-26 Updated: 2023-10-26 Resolved: 2017-10-31 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ? |
| Affects Version/s: | 1.0.11 |
| Fix Version/s: | 1.1.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Thompson (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Sprint: | 2017-20, 2017-21, 2017-22 |
| Description |
|
If you have a multi node system with replication then if UM1 is to go down then the system will automate failover to another UM, however say UM2 has it' server-id value changed to 1 from 2. This is bad and we should simply make UM2 the new master only. This will avoid problems with InnoDB replication (no impact to ColumnStore tables) Presumably this was done for a reason so should make sure that we cover this. |
| Comments |
| Comment by David Hill (Inactive) [ 2017-10-23 ] | ||||||||||||||||
|
fixed 1.0.12 commit 58a77b708cb0306892cbfd7a1be3b72246a0dbf6 procmon/processmonitor.cpp | 13 ++++++------- 1.1.1 commit 8706f0a9ef39329331761980df483806f942b0b8 procmon/processmonitor.cpp | 6 +++--- 1.2 commit 4e7e8487f7c711405dd1fccde17c84b181c3dfd3 procmon/processmonitor.cpp | 6 +++--- ------------------------------------------------------------------------------ To test: install system with replication set, do a failover on um1 to cause um1 to go active. Bring back um1. check both nodes to make sure the ID server-id doesnt change | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-26 ] | ||||||||||||||||
|
Build tested: Github source for 1.0.12 /root/columnstore/mariadb-columnstore-server Merge pull request #69 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #297 from mariadb-corporation/ Build tested: Github source for 1.1.1 /root/columnstore/mariadb-columnstore-server Merge pull request #72 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #299 from mariadb-corporation/mcol-667 Mcol 667 For both 1.0 and 1.1, I did a 2pm combo system. After the system came up, both PMs have "server-id = 1" in my.cnf. server-id should be unique among servers For 1.1, PM1: MariaDB [(none)]> show master status;
-----------------
----------------- MariaDB [(none)]> show slave status; PM2: MariaDB [(none)]> show master status;
-----------------
----------------- MariaDB [(none)]> show slave status; | ||||||||||||||||
| Comment by David Hill (Inactive) [ 2017-10-26 ] | ||||||||||||||||
|
fixed.... commit af35345273b85b55f755303abc8cb0d1bea5fb89 mcol-938 - fixed pm server ids procmon/processmonitor.cpp | 29 ++--------------------------- [root@ip-172-30-0-161 mysql]# grep server-id my.cnf System Network Configuration Module Name Module Description NIC ID Host Name IP Address [root@ip-172-30-0-161 mysql]# ssh 172.30.0.152 ------------------------------------ Take Control of Your Data with MariaDB www.mariadb.com --------------------------------------------- Please refer to the README file for [root@ip-172-30-0-152 ~]# home | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-27 ] | ||||||||||||||||
|
Build tested: Github source for 1.1.1 /root/columnstore/mariadb-columnstore-server Merge pull request #72 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine mcol-938 - fixed pm server ids I did a combo installation and still have the same issues. Both PMs have server id of 1. | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-27 ] | ||||||||||||||||
|
Build tested: Github source for 1.0.12 /root/columnstore/mariadb-columnstore-server Merge pull request #69 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #304 from mariadb-corporation/ | ||||||||||||||||
| Comment by David Hill (Inactive) [ 2017-10-30 ] | ||||||||||||||||
|
test fix, working for combo 2pm now... need to retest other install types from pm2 [root@ip-172-30-0-152 ~]# home Copyright (c) 2000, 2017, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show slave status\G;
| ||||||||||||||||
| Comment by David Hill (Inactive) [ 2017-10-30 ] | ||||||||||||||||
|
fixed develop-1.1 commit 6277371669953e000ae91ea92466d0f4907722f4 oam/install_scripts/rsync.sh | 40 +++++++++++++++++++++------------------- | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-31 ] | ||||||||||||||||
|
Build tested: 1.1.1-1 Centos 7 rpm package released to the shared today. I performed an installation of 2pm combo, the server-id are correct (pm1=1, pm2=2), and the MySQLRep flag was setup to y. But databases on PM1 are not being replicated to PM2. | ||||||||||||||||
| Comment by David Hill (Inactive) [ 2017-10-31 ] | ||||||||||||||||
|
tried to reproduce Daniels issue with both binary and rpm packages and couldn't. I was able to create database and tables and they were getting replicated on pm2.. ma getso Name : mariadb-columnstore-platform | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-31 ] | ||||||||||||||||
|
Build verified: 1.1.1-1 rpm package released to QA today Verified, Fixed Build tested: 1.0.12-1 GitHub source Still having an issue /root/columnstore/mariadb-columnstore-server Merge pull request #69 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #304 from mariadb-corporation/ Tested on a 2um2pm stack. Because of the issues in 1. Installed a 2um2pm stack with mysqlrep off Testing steps 4. suspended um1 VM (in vagrant) At the end, both UM1 and UM2 have the same server-id, 2. | ||||||||||||||||
| Comment by Daniel Lee (Inactive) [ 2017-10-31 ] | ||||||||||||||||
|
This ticket is now for 1.1.1-1 only. |