pt-heartbeat does not detect master server id if it can't connect to the remote master
Bug #1097997 reported by
Stuart Cianos
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Triaged
|
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.
Revision history for this message
| Stuart Cianos (scianos-s) wrote | #1 |
| 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 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/