[MCOL-2269] mysql replication script, rsync.sh, isnt copying over idbdata1 file Created: 2019-04-02  Updated: 2021-04-19  Resolved: 2021-02-20

Status: Closed
Project: MariaDB ColumnStore
Component/s: N/A
Affects Version/s: 1.2.5
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: David Hill (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 2
Labels: None
Environment:

2um 2pm amazon ec2 setup


 Description   

Customer added UM2 and was getting error that InnoDB tables didnt exist UM2 after the system was running. Found out that the file 'idbdata1' wasnt syned with UM1 version. It was smaller.

Issue looks to be that the ibdata1 file isnt getting copied over via the rsync command

 Comments   
Comment by David Hill (Inactive) [ 2019-06-19 ]

This needs to be prioritized in scheduled in a upcoming release. Its an issue that customers have run into multiple times.

Comment by David Hill (Inactive) [ 2019-10-03 ]

Workaround - Anytime a new UM or Combination PM is added with Replication enabled, you will need to do the following:

FROM NEW MODULE

//stop the mysqld service

  1. cd ../mariadb/columnstore/mysql/mysql-columnstore stop
  2. cd db
  3. mv idbdata1 /tmp/.
    //scp idbdata1 from UM1 OR Combinated PM1, fill in the correct path
  4. scp xxx.xxx.xxx.xxx@../mariadb/columnstore/mysql/db/idbdata1 .
    //start the service
  5. cd ..
  6. cd ../mariadb/columnstore/mysql/mysql-columnstore start
Comment by David Hill (Inactive) [ 2019-11-21 ]

It looks like there are more innodb specific files that arent being moved. Those would be the files in the mysql directory, which is specifically excluded. Looks like this script was specific done to just move CS related files. It needs to be reworked to move non-CS database files also.

Comment by Todd Stoffel (Inactive) [ 2021-02-20 ]

Obsolete

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