Source config from SST script

Bug #1168361 reported by Raghavendra D Prabhu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Invalid
Undecided
Raghavendra D Prabhu

Bug Description

As described in https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1167331/comments/5 it would be better if custom configuration is possible for SST, Xtrabackup SST atleast.

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

Why is sourcing defaults file (my.cnf) not enough? Is there a separate configuration file for xtrabackup?

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Options to innobackupex (some which are in turn passed to xtrabackup) cannot be passed through my.cnf

To give an example, so may want to pass --parallel 6 to spawn 6
data copying threads or --stream=xbstream among others.

Revision history for this message
Alex Yurchenko (ayurchen) wrote :

If you can pass options to mysqld_safe (which is a shell script) via my.cnf, you surely can pass them to innobackupex. Since xtrabackup requires my.cnf anyways, it makes no sense that innobackupex can't use it.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Yes, it cannot use it currently. Only xtrabackup reads from
my.cnf, innobackupex does not.

Changed in percona-xtradb-cluster:
milestone: none → 5.5.30-24.8
status: New → Triaged
assignee: nobody → Raghavendra D Prabhu (raghavendra-prabhu)
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

@Alexey,

The options I was thinking of -- throttle, parallel and use-memory -- should work from [xtrabackup] my.cnf as well. (since xtrabackup handles them directly).

I don't see any other options here http://www.percona.com/doc/percona-xtrabackup/innobackupex/innobackupex_option_reference.html which may be useful with SST.

(--compress requires manual decompression on joiner end, so it won't help, --databases, --include, --tables-file are good for partial backups/restores but I am not sure how they can be used here).

Changed in percona-xtradb-cluster:
milestone: 5.5.30-24.8 → none
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

I don't think anything is required from joiner end since all
configuration can be done in my.cnf.

Only on receiver end, some manual decompression/decryption etc.
will be required.

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :
Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Marking this as invalid for now since it has been dealt in lp:1179405 (though differently).

Changed in percona-xtradb-cluster:
status: Triaged → Invalid
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.