pt-heartbeat does not detect master server id if it can't connect to the remote master

Reported by Stuart Cianos on 2013-01-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Undecided
Unassigned

Bug Description

Currently, the pt-heartbeat tool cannot detect the master server ID for a given host automatically if it cannot connect to the remote master, or if the remote master is down/unavailable. The supplied patch allows pt-heartbeat to get the information via show slave status, which then falls back to the old method if not successful.

Diff against 2.1.8 is attached.

Changed in percona-toolkit:
status: New → Triaged
summary: - Pt-heartbeat does not detect master server id if it can't connect to the
+ pt-heartbeat does not detect master server id if it can't connect to the
remote master
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers