pt-heartbeat --skew doesn't work

[snowave]

1.-interval
type: float; default: 1.0

How often to update or check the heartbeat --table. Updates and checks begin on the first whole second then repeat every --interval seconds for --update and every --interval plus --skew seconds for --monitor.

it's meaning, time of every interval of monitor is --interval + --skew, but i found ,

./pt-heartbeat --skew=5 --database=test --create-table --master-server-id=55 h=127.0.0.1,u=root,P=3306,D=test --monitor

--skew=5 ,on works on the first time， the next acitons still use default --interval （1s） to check slave lags， not add --skew。

2.
--master-server-id
type: string

Calculate delay from this master server ID for --monitor or --check. If not given, pt-heartbeat attempts to connect to the server’s master and determine its server id.

but, i test it , orrur error about it:

pt-heartbeat --database=test --create-table h=127.0.0.1,u=root,P=3306,D=test --monitor
The --master-server-id option must be specified because the heartbeat table `test`.`heartbeat` uses the server_id column for --update or --check but the server's master could not be automatically determined.

3. below command, if i did't use --master-server-id, it won't work, it did't work as some detail in the documention :

Try to discover slave servers recursively, to the specified depth. After discovering servers, run the check on each one of them and print the hostname (if possible), followed by the slave delay.

pt-heartbeat --recursion-method=processlist --recurse=2 --database=test --create-table h=127.0.0.1,u=root,P=3306,D=test --check

in m-s-s replica, i found than it couldn't determine the server's master automatically .

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1141