pt-heartbeat does not appear to support timezones/problem with daylight saving time switch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
As filed here:
https:/
pt-heartbeat's table schema does not appear to support timezones, and the times written to the browserid.heartbeat database are in PST8PDT rather than UTC. During the "fall back" hour the Nagios mysql_repl check reports false alarms of 3600.0 seconds of lag, which resolves once the clock ticks over to 2am a second time.
01:03 < nagios-svc-scl2> Sun 01:03:10 PST [140] db3.iddb.
02:03 < nagios-svc-scl2> Sun 02:03:09 PST [155] db3.iddb.
This resulted in a one hour gap in production replication lag monitoring, during which one manual comparison of slaves' log position vs. master log position was performed.
Note that the timestamp stored in the database between 01:00:00 PST (-0800) and 01:59:59 PST (-0800) is accurate in PST (-0800); that is, it reads "01:xx" rather than "02:xx" or some other value. I do not have data for 01:00:00 PDT (-0700) to 01:59:59 PDT (-0700).
tags: | added: pt-heartbeat tz |
Changed in percona-toolkit: | |
status: | New → Confirmed |
Hi Sheeri,
Seems like this is a duplicate of https:/ /bugs.launchpad .net/percona- toolkit/ +bug/886059 -- do any of the workarounds in there solve the issue for you?
If they do, what do you think the tool should do here? I can think of arguments for and against respecting the timezone, and if this can be sidestepped by using --set-vars, I'm leaning towards leaving the current behavior but adding a warning in the docs -- But I'm a developer, so an user's opinion would be quite welcome.