Percona XtraBackup moved to https://jira.percona.com/projects/PXB

innobackupex does not log MASTER_PORT in xtrabackup_slave_info

  1. Series 2.2
  2. Bug #1252822
Bug #1252822 reported by Michael Coburn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Triaged
Low
Unassigned
Percona XtraBackup moved to https://jira.percona.com/projects/PXB future-2.3-releases
2.1
Triaged
Low
Unassigned
Percona XtraBackup moved to https://jira.percona.com/projects/PXB future-2.1-releases
2.2
Triaged
Low
Unassigned
Percona XtraBackup moved to https://jira.percona.com/projects/PXB future-2.2-releases
2.3
Triaged
Low
Unassigned
Percona XtraBackup moved to https://jira.percona.com/projects/PXB future-2.3-releases

Bug Description

Hi,

When taking a backup from a MySQL server on a non-standard port, I think we should log the MASTER_PORT information in xtrabackup_slave_info file as part of the CHANGE MASTER TO statement. This is what currently prints for a backup taken using --socket and @@port = 3328:

CHANGE MASTER TO MASTER_LOG_FILE='bin.000483', MASTER_LOG_POS=787644212,

I think it should be:

CHANGE MASTER TO MASTER_LOG_FILE='bin.000483', MASTER_LOG_POS=787644212, MASTER_PORT=3328',

Revision history for this message
Miguel Angel Nieto (miguelangelnieto) wrote :

Issue confirmed. Maybe in order to make the bugfix easier we should make this the default behaviour. Even if the port is 3306, add it.

Changed in percona-xtrabackup:
status: New → Confirmed
Alexey Kopytov (akopytov)
tags: added: low-hanging-fruit
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/PXB-899

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

Other bug subscribers

Remote bug watches

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