Blog Tag: geo-distributed

We’ve just recently brought our Continuent Tungsten AMIs up to the current release level of our flagship products, Tungsten Cluster and Tungsten Replicator, and would like to invite users to give them a test drive!

Why does the DIY approach fail to deliver vs. the Tungsten Clustering solution for geo-distributed MySQL multimaster deployments? Before we dive into the 10 reasons, note why commercially-supported enterprise software is less risky and in fact less costly.

In this blog post we will define what a split-brain scenario means in a MySQL database cluster, and then explore how a Tungsten MySQL database cluster reacts to a split-brain situation.

This blog explains why the Tungsten rollback error exists and why it's important.

In this blog post we will discuss how the managed cross-site replication streams work in a Composite Multi-Master Tungsten Cluster for MySQL, MariaDB and Percona Server.

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.

Enterprises require high availability for their business-critical applications. Even the smallest unplanned outage or even a planned maintenance operation can cause lost sales, productivity, and erode customer confidence. Additionally, updating and retrieving data needs to be robust to keep up with user demand.

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.