XtraBackup test framework force to use original my.cnf during prepare

Bug #1072695 reported by Sergei Glushchenko on 2012-10-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Low
Alexey Kopytov
2.0
Won't Fix
Undecided
Unassigned
2.1
Won't Fix
Undecided
Unassigned
2.2
Fix Released
Low
Alexey Kopytov

Bug Description

innobackupex bash function always invoke innobackupex script with following options:

IB_ARGS="--defaults-file=${MYSQLD_VARDIR}/my.cnf --user=root \
--socket=${MYSQLD_SOCKET} --ibbackup=$XB_BIN"

which is incorrect in the case of prepare, when backup-my.cnf should be used (--defaults-file option overrides default backup-my.cnf).

This cause some problems when we want to test backup-my.cnf, or when default my.cnf and backup-my.cnf are not identical, for example when we deal with separate doublewrite file.

Related branches

Changed in percona-xtrabackup:
status: New → Confirmed
description: updated
summary: XtraBackup test framework force to use original my.cnf during prepare
- and copy back
description: updated
Stewart Smith (stewart) on 2012-12-10
tags: added: test
Alexey Kopytov (akopytov) wrote :

This was fixed in the linked branch by changing innobackupex so that $backup_dir/backup-my.cnf is always used on --apply-log (even if there's a defaults file specified on the command line).

I don't think there's much use in overriding backup-my.cnf on prepare. In rare cases when someone somewhere may want to do so, one can always replace or edit backup-my.cnf to override some parameters.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-86

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers