wsrep_sst_rsync ignores log_group_home_dir
Bug #1218944 reported by
joffrey92
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
High
|
Vladislav Klyachin | |||
| 5.6 |
Fix Released
|
High
|
Vladislav Klyachin | |||
Bug Description
When using rsync protocol, the log_group_home_dir is ignored, and log files are not managed for the copy.
innodb_
datadir = /var/lib/mysql
Rsync command:
23260 rsync -avP db1 db2 db3 ibdata1 ib_logfile0 ib_logfile1 mysql performance_schema test /var/lib/mysql/
This is an issue, as log files do not match any more the data for the cloned server
(...)
130830 13:16:19 InnoDB: Error: page 421505 log sequence number 265303269819
InnoDB: is in the future! Current system log sequence number 2507458062.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
(...)
Galera+MariaDB 5.5.29
To post a comment you must log in.
That's right. ATM rsync SST does not look into my.cnf at all