pt-slave-find ignores host port, reports incorrect replication chain
Bug #1220774 reported by
Luis Motta Campos
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Confirmed
|
Undecided
|
Unassigned |
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:
master001:3306
* read-slave001:3306
* delayed-
** delayed-
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:
master001
+ read-slave001
+ delayed-slave001
Changed in percona-toolkit: | |
status: | New → Confirmed |
To post a comment you must log in.
I cannot repeat this with versions 2.2.20 and 3.0.2