Continuent provides multiple methods out of the box to monitor the cluster health. It integrates with monitoring and alerting tools like Nagios/NRPE, Zabbix, and Pagerduty. This blog post shows you the thinking behind each included Tungsten Cluster monitoring tool, and when to use which tool.
This blog explains why the Tungsten rollback error exists and why it's important.
What are some reasons and strategies for performance tuning Tungsten Replicator when applying to a MySQL target database?
This blog covers INI vs Staging configurations for Secure Shell.
In this blog post we will discuss how to best integrate various Continuent-bundled cluster monitoring solutions with PagerDuty (pagerduty.com), a popular alerting service.
One important way to protect your MySQL / MariaDB / Percona Server data is to keep your Tungsten Clustering software up-to-date; but how can you achieve this with zero-downtime?
Learn about the two different methods for installing, updating and upgrading Tungsten Clustering software for MySQL / MariaDB / Percona Server.
Your MySQL database cluster contains your most business-critical data; in this post, we discuss how to ensure proper performance under load.
This post covers some standard Nagios checks that would keep your MySQL / MariaDB / Percona Server cluster nodes healthy.
A robust monitoring setup is essential for cluster health and viability - if your replicator goes offline and you do not know about it, then that Replica becomes effectively useless because it has stale data. This means keeping a close watch on the health of the MySQL / MariaDB / Percona Server database nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.
