pmp-check-mysql-replication-delay reports ok if server is not configured as a slave
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Monitoring Plugins |
Fix Released
|
Low
|
Unassigned |
Bug Description
[root@cron01 ~]# mysql ... -e "show slave status\G"
[root@cron01 ~]# /usr/lib64/
OK 0 seconds of replication delay | replication_
It seems to be logical to return UNKNOWN in such case, isn't it?
We discussed this with Jay Janssen in #44493
He said:
Firstly, it’s intended that you use pmp-check-
As far as your specific problem, I do think it is supposed to return UNKNOWN in that case, so it may be a bug. I found a similar report from a few years ago that should have been fixed: https:/
description: | updated |
Changed in percona-monitoring-plugins: | |
status: | Opinion → Confirmed |
importance: | Undecided → Low |
tags: | added: nagios |
Changed in percona-monitoring-plugins: | |
status: | Confirmed → Fix Committed |
Changed in percona-monitoring-plugins: | |
status: | Fix Committed → Fix Released |
It returns OK because in some cases, you want it to report OK on all the servers despite they are configured with slave or not. So like a generic check. UNKNOWN usually means unable to determine the slave status. If the replica is not configured, there is no reason why delay check should fail. To be alerted whether the replication is running or not at all, that's another script for - pmp-check- mysql-replicati on-running.