[MCOL-3705] Combo installation with schema-sync does not create schema on pm2 Created: 2019-12-30  Updated: 2020-01-03  Resolved: 2020-01-01

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.4.2
Fix Version/s: Icebox

Type: Bug Priority: Critical
Reporter: Daniel Lee (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MCOL-3702 postConfigure Replication Error Closed

 Description   

Build tested: 1.4.2-1 (Azure build 20191224.6)

During postConfigure, I enabled schema-sync:

NOTE: The MariaDB ColumnStore Schema Sync feature will replicate all of the
schemas and InnoDB tables across the User Module nodes. This feature can be enabled
or disabled, for example, if you wish to configure your own replication post installation. MariaDB ColumnStore Schema Sync feature, do you want to enable? [y,n] > y

But when I create databases and tables on PM1, schemas are not synced to PM2. In the /etc/columnstore/Columnstore.xml file, <MySQLRep> is set to 'y'. I noticed that in the /etc/my.cnf.d/columnstore.cnf file, server-id is set to 1 and commented out on both PMs.

I shutdown the system, setup server-id to 1 and 2 for PM1 and PM2, respectively. Restarted the system. Schema-sync was still not working.

 Comments   
Comment by Todd Stoffel (Inactive) [ 2020-01-01 ]

Schema sync/ replication is not actually working since the script fails. This has already been reported in MCOL-3702

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