Closed
Bug 856603
Opened 13 years ago
Closed 13 years ago
mozsql: replication check
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: scabral, Assigned: bjohnson)
References
Details
(Whiteboard: [2013q2] April)
1) replication status check - expand upon regular replication check - not just threshold (e.g. warn if X seconds behind, crit if Y seconds behind), but know if it's catching up or lagging even more.
get repl info, wait 10 seconds, get repl info again, compare rates. What makes an increase fast or slow?
Also compare sql thread query to see if it's the same. If it is the same and rate is increasing, check can output that there's a long-running query in the sql thread.
If replication isn't working, display master server host, whether or not the IO_THREAD and SQL_THREADs are running, and what the delay is (including rate and sql thread).
| Reporter | ||
Updated•13 years ago
|
Whiteboard: [2013q2] → [2013q2] April
| Reporter | ||
Updated•13 years ago
|
Assignee: server-ops-database → bjohnson
| Assignee | ||
Comment 1•13 years ago
|
||
This is completed and tested. What's the best way to get this out to become a nagios check? I noticed other nagios checks aren't in the mysql2 module. Should I open a ticket for Server Ops?
| Reporter | ||
Comment 2•13 years ago
|
||
Yes, open a bug for Server Ops. Make sure you give them the options they'll need, and make sure the script is nagios-ready (with the proper output codes). If you're not sure about what that all is, I can work with you on it.
They should test it on one or 2 machines first.
| Reporter | ||
Comment 3•13 years ago
|
||
All that's left is docs and license, which are in bug 883210.
Updated•11 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•