pt-heartbeat 2.1.8 reports false lag without --monitor
Bug #1103198 reported by
Daniel Nichter
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona Toolkit moved to https://jira.percona.com/projects/PT |
Invalid
|
High
|
Daniel Nichter | ||
Bug Description
With no --monitor running, 2.1.8 does:
$ bin/pt-heartbeat --monitor -F /tmp/12346/
0.50s [ 0.01s, 0.00s, 0.00s ]
1.50s [ 0.03s, 0.01s, 0.00s ]
2.50s [ 0.07s, 0.01s, 0.01s ]
but 2.1.7 did:
$ ../pt-heartbeat
0.00s [ 0.00s, 0.00s, 0.00s ]
0.00s [ 0.00s, 0.00s, 0.00s ]
0.00s [ 0.00s, 0.00s, 0.00s ]
Revision history for this message
| Daniel Nichter (daniel-nichter) wrote | #1 |
| tags: | added: pt-heartbeat |
| Changed in percona-toolkit: | |
| status: | In Progress → Invalid |
| Changed in percona-toolkit: | |
| milestone: | 2.1.9 → none |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
I was mistaken: this isn't a new bug, it's just a weird result when running 2.1.8 then 2.1.7.