Many of you who use MySQL replication have requested that we do more to assist you in monitoring and troubleshooting issues with various replicaton topologies. Right now, we’re in the process of designing replication monitoring enhancements for our current Monitoring and Advisory Service so I thought I’d request your input on what you’d like to see.
The most common questions I hear that come up with respect to replication monitoring are these:
- Are there any global replication issues in my monitored replication topologies?
- Do I have any down master servers?
- Do I have any down slave servers?
- Are my SQL and I/O slave threads running on my slaves?
- Is the replication latency between any master and slave too high?
- What are the top ?N? worst performing (highest latency) slaves?
- Have any slaves experienced a replication-specific error?
- What are the last ?N? errors in a master or slave error log?
- Are my binary logs using too much space on my master?
- Are there too many binary log files on my master?
- What is the current replication configuration of a selected master or slave server?
What other answers would help you better monitor and maintain your MySQL replication setups? Please respond to this thread.
Robin Schumacher
Director, Product Management,
MySQL AB
rschumacher@mysql.com
Edited 1 time(s). Last edit at 05/05/2007 09:58PM by Edwin DeSouza.