Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

LP #1513520: xtrabackup doesn't handle --slave-info option well with PXC

Description

**Reported in Launchpad by kedar last update 11-12-2015 02:24:21

Xtrabackup Version: xtrabackup 2.3.2
Server Version: 5.6.26-74.0-56-log Percona XtraDB Cluster (GPL), Release rel74.0, Revision 624ef81, WSREP version 25.12, wsrep_25.12

Backup Command:
innobackupex --defaults-file=/etc/mysql/my.cnf --user=root --slave-info --tmpdir=/tmp --stream=tar ./ 2>/tmp/bkup.log | gzip > backup.tar.gz

Backup terminates without error.

Tail of backup log:

YYMMDD HH:MM:SS Executing LOCK BINLOG FOR BACKUP...
Failed to get master binlog coordinates from SHOW SLAVE STATUS
This means that the server is not a replication slave. Ignoring the --slave-info option

After the message "ignoring slave-info" backup actually terminates; it should continue and finish clean backup.

As such --slave-info is irrelevant to PXC and xtrabackup works well without that option though it should handle correctly.

Thanks.

Environment

None

Smart Checklist

Activity

Show:

lpjirasync January 19, 2018 at 2:24 PM

**Comment from Launchpad by: Edwin on: 11-12-2015 02:22:35

Thank you Serfgei!

*Edwin Wang *
MySQL Database Consultant

Pythian — love your data

ewang <kukreja@pythian.com>@pythian.com <kukreja@pythian.com> | Skype name:
pythianewang

Tel: +1 613 565 8696 ext. 1289

Mobile: 604-230-7281

On Thu, Dec 10, 2015 at 5:48 PM, Sergei Glushchenko <
1513520@bugs.launchpad.net> wrote:

> ** Changed in: percona-xtrabackup/2.3
> Milestone: future-2.3-releases => 2.3.3
>
> –
> You received this bug notification because you are subscribed to a
> duplicate bug report (1511893).
> https://bugs.launchpad.net/bugs/1513520
>
> Title:
> xtrabackup doesn't handle --slave-info option well with PXC
>
> Status in Percona XtraBackup:
> Fix Released
> Status in Percona XtraBackup 2.3 series:
> Fix Released
>
> Bug description:
> Xtrabackup Version: xtrabackup 2.3.2
> Server Version: 5.6.26-74.0-56-log Percona XtraDB Cluster (GPL), Release
> rel74.0, Revision 624ef81, WSREP version 25.12, wsrep_25.12
>
> Backup Command:
> innobackupex --defaults-file=/etc/mysql/my.cnf --user=root --slave-info
> --tmpdir=/tmp --stream=tar ./ 2>/tmp/bkup.log | gzip > backup.tar.gz
>
> Backup terminates without error.
>
> Tail of backup log:
>
> YYMMDD HH:MM:SS Executing LOCK BINLOG FOR BACKUP...
> Failed to get master binlog coordinates from SHOW SLAVE STATUS
> This means that the server is not a replication slave. Ignoring the
> --slave-info option
>
>
> After the message "ignoring slave-info" backup actually terminates; it
> should continue and finish clean backup.
>
> As such --slave-info is irrelevant to PXC and xtrabackup works well
> without that option though it should handle correctly.
>
> Thanks.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/percona-xtrabackup/+bug/1513520/+subscriptions
>

–

–

lpjirasync January 19, 2018 at 2:24 PM

**Comment from Launchpad by: Sergei Glushchenko on: 09-12-2015 22:54:58

https://github.com/percona/percona-xtrabackup/pull/131

lpjirasync January 19, 2018 at 2:24 PM

**Comment from Launchpad by: Max Bubenick on: 09-11-2015 18:19:20

This is not only affecting PXC but any server not running as slave.

lpjirasync January 19, 2018 at 2:24 PM

**Comment from Launchpad by: Sergei Glushchenko on: 09-11-2015 03:55:26

Lets continue the backup instead of failing aborting it in this case as 2.2.x did.

Done

Details

Assignee

Reporter

Labels

Priority

Smart Checklist

Created January 19, 2018 at 2:24 PM
Updated January 19, 2018 at 2:24 PM
Resolved January 19, 2018 at 2:24 PM