pt-heartbeat failure in replication hierarchy with GTID
Bug #1733012 reported by
monty solomon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
New
|
Undecided
|
Unassigned | ||
Bug Description
pt-heartbeat fails to work on a slave in a replication hierarchy unless there is a row in the table for its parent in the hierarchy.
pt-heartbeat --host localhost -D heartbeat --check --no-insert-
No row found in heartbeat table for server_id 639407132.
At least one row must be inserted into the heartbeat table for server_id 639407132.
Please read the DESCRIPTION section of the pt-heartbeat POD.
We don't want to write to the heartbeat table on any slaves since that will add errant GTIDs.
pt-heartbeat should be able to be run in a mode where it can be instructed to use the row in the table as the master.
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/