pt-slave-find ignores host port, reports incorrect replication chain

Bug #1220774 reported by Luis Motta Campos on 2013-09-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to

Bug Description

I'm running

    pt-slave-find 2.1.9
    pt-slave-find 2.2.4

This is my command line arguments:

    pt-slave-find --report-format hostname h=master001

My database replication chain looks like this:

* read-slave001:3306
* delayed-slave001:3307
** delayed-slave001:3306

pt-slave-find assumes the database port is always 3306, ignores the replication using the unconventional port 3307 and (unfortunately) finds the replication slave running in port 3306 in the same host.

This is what pt-slave-find reports:

+ read-slave001
+ delayed-slave001

Changed in percona-toolkit:
status: New → Confirmed
Sveta Smirnova (svetasmirnova) wrote :

I cannot repeat this with versions 2.2.20 and 3.0.2

Sveta Smirnova (svetasmirnova) wrote :

Not repeatable for me with 2.2.4 as well:

$ ~/mysql_packages/percona-toolkit-2.2.4/bin/pt-slave-find --report-format hostname h=,P=3371,u=root

Probably using remote hosts is required to repeat this bug.

Percona now uses JIRA for bug reports so this bug report is migrated to:

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

Other bug subscribers