mysqldump --single-transaction in maria-5.1-mwl136 uses an absolute path to master_log_file in CHANGE MASTER
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
High
|
Kristian Nielsen |
Bug Description
When using mysqldump --single-
CHANGE MASTER TO MASTER_
Using absolute paths for MASTER_LOG_FILE will cause the slave to stop with a "cannot open first file" error. By contrast, normal mysqldump would return:
CHANGE MASTER TO MASTER_
To reproduce:
# default mysqldump from RPM
mysqldump --single-
CHANGE MASTER TO MASTER_
# mysqldump from wl139
../client/mysqldump --single-
CHANGE MASTER TO MASTER_
../client/mysqldump --master-data -uroot --protocol=tcp --port=19300 test | grep -i change
CHANGE MASTER TO MASTER_
Related branches
Changed in maria: | |
assignee: | nobody → Kristian Nielsen (knielsen) |
milestone: | none → 5.3 |
milestone: | 5.3 → none |
Changed in maria: | |
status: | New → Confirmed |
Changed in maria: | |
status: | Fix Committed → Fix Released |
Thanks for spotting this!
The underlying issue is different output between these two statements:
MariaDB [test]> show master status; ------- -----+- ------- --+---- ------- ---+--- ------- ------- -+ ------- -----+- ------- --+---- ------- ---+--- ------- ------- -+ ------- -----+- ------- --+---- ------- ---+--- ------- ------- -+
+------
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------
| mysql-bin.000051 | 240 | | |
+------
1 row in set (0.00 sec)
MariaDB [test]> SHOW STATUS LIKE 'binlog_snapshot_%' ------- ------- ------+ ------- ------- ------+ ------- ------- ------+ ------- ------- ------+ snapshot_ file | ./mysql-bin.000051 | snapshot_ position | 240 | ------- ------- ------+ ------- ------- ------+
-> ;
+------
| Variable_name | Value |
+------
| binlog_
| binlog_
+------
2 rows in set (0.00 sec)
Note the leading `./' in the second version; this should be removed.