[MCOL-942] Setting up of the Master/Slave Replication should not be done on start system Created: 2017-09-27  Updated: 2017-12-05  Resolved: 2017-12-05

Status: Closed
Project: MariaDB ColumnStore
Component/s: ProcMgr
Affects Version/s: 1.0.11, 1.1.0
Fix Version/s: 1.0.12

Type: New Feature Priority: Minor
Reporter: David Hill (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

aws 2um / 2pm test system

Sprint: 2017-24

 Description   

Currently in 1.0, the master/slave is setup at the end of postConfigure AND will also be resetup when a restartsystem or system servers are rebooted.
In 1.1, this logic is only in ProcMgr for startsystem.

It is recommended that this not be setup everything the system is restarted. I did a reboot test and the master/slave setup remain when I took out the step in ProcMgr to set it up on startsystem.

So for 1.0 and 1.1, it should only be initially setup in postConfigure. and removed from the startsystem in ProcMgr. It will still be called by procmgr when the master node needs to be changed.

 Comments   
Comment by David Hill (Inactive) [ 2017-09-27 ]

might have jumped the gun on master/slave is setup after reboot. I get the following error

CREATE TABLE `brptab1` ( `id` int(11) NOT NULL, `name` varchar(100) NOT NULL ) ENGINE=InfiniDB DEFAULT CHARSET=utf8;
ERROR 1178 (42000): The storage engine for the table doesn't support IDB-4016: DML and DDL statements for Columnstore tables can only be run from the replication master.
MariaDB [david]>
MariaDB [david]>
MariaDB [david]> show master status;
------------------------------------------------------+

File Position Binlog_Do_DB Binlog_Ignore_DB

------------------------------------------------------+

mysql-bin.000007 327    

------------------------------------------------------+
1 row in set (0.00 sec)

MariaDB [david]>

Comment by David Hill (Inactive) [ 2017-11-28 ]

testing - should see the distribute to pm only on local-query and combo um/pm installs. you should see this on separate install when local-query is disabled

Nov 28 17:25:10 ip-172-30-0-59 ProcessMonitor[13973]: 10.283781 |0|0|0| D 18 CAL0000: runMasterDist function called
Nov 28 17:25:10 ip-172-30-0-59 ProcessMonitor[13973]: 10.284224 |0|0|0| D 18 CAL0000: cmd = /usr/local/mariadb/columnstore/bin/rsync.sh 172.30.0.161 'Calpont1' /usr/local/mariadb/columnstore 1 > /tmp/master-dist_pm1.log
Nov 28 17:25:10 ip-172-30-0-59 ProcessMonitor[13973]: 10.680937 |0|0|0| D 18 CAL0000: runMasterDist: Success rsync to module: pm1
Nov 28 17:25:10 ip-172-30-0-59 ProcessMonitor[13973]: 10.680990 |0|0|0| D 18 CAL0000: cmd = /usr/local/mariadb/columnstore/bin/rsync.sh 172.30.0.152 'Calpont1' /usr/local/mariadb/columnstore 1 > /tmp/master-dist_pm2.log
Nov 28 17:26:10 ip-172-30-0-59 ProcessMonitor[13973]: 10.966580 |0|0|0| D 18 CAL0000: runMasterDist: Success rsync to module: pm2

and verified the server-id in the different my.cnf files are setup with um1 or active um being '1'.

Comment by David Hill (Inactive) [ 2017-11-28 ]

https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/331

Comment by Ben Thompson (Inactive) [ 2017-11-28 ]

Reviewed / Merged

Comment by Daniel Lee (Inactive) [ 2017-12-05 ]

Build verified: GitHub source

1.0.12-1

[root@localhost ~]# cat mariadb-columnstore-1.0.12-1-centos7.x86_64.bin.tar.txt
/root/columnstore/mariadb-columnstore-server
commit 25e9d054cd3d05683fade1b974e1730316d256ed
Merge: 89b2ea1 7c52a83
Author: David.Hall <david.hall@mariadb.com>
Date: Tue Nov 21 10:49:11 2017 -0600

Merge pull request #79 from mariadb-corporation/MCOL-954-1.0

MCOL-954 Init vtable state

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit b112e826a2793228f5f3c1312fec5291fc1d8bf5
Merge: 7c2640f b657938
Author: David.Hall <david.hall@mariadb.com>
Date: Fri Dec 1 16:17:28 2017 -0600

Merge pull request #338 from mariadb-corporation/MCOL-1068

MCOL-1068 Improve compression_ratio() procedure

Verified both 1um2pm localquery and 2pm combo systems. Initial installation and restart system.

Generated at Thu Feb 08 02:24:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.