- Products & Solutions
- About Us
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.
When deploying Tungsten Clustering for MySQL / MariaDB / Percona Server, we always recommend an odd number of Manager nodes in each cluster. Let's take a look at how having an odd number of Managers helps keep a Tungsten Cluster functioning and avoids data corruption scenarios (i.e. "split brain").
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.
This post covers some standard Nagios checks that would keep your MySQL / MariaDB / Percona Server cluster nodes healthy.
This blog discusses some of the ways you can configure your MySQL / MariaDB / Percona Server slaves using Tungsten Clustering.
One nice thing about Tungsten Clustering is that you need just a single command to move the master role to another host in your cluster.
The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.
In this blog post we will discuss the basics of how to implement and use filters in the Tungsten Replicator.
Managing a single cluster takes time and attention, and handling multiple clusters spread out over many sites is even more demanding. Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. You are able to view, monitor and maintain all of your clusters all in one place.
Achieving software upgrades without downtime is a challenge that few software products can handle, or even try to. Tungsten Clustering is one that can!
Think about it - your application needs to be online and available for the business to run. Downtime is to be avoided like the plague. The buzz is all about five nines of uptime.
How do we as systems architects, DBAs and sysadmins create an environment where routine maintenance is not a thing to be feared and put off, but embraced to allow for proper and needed updates and upgrades to take place?