How To Configure Tungsten Connector For Load Balancing, Read/Write Splitting, Automatic Failover And Online Maintenance

How To Configure Tungsten Connector For Load Balancing, Read/Write Splitting, Automatic Failover And Online Maintenance 

Tungsten clusters use the Tungsten Connector to ensure your applications transparently connect to the master. This enables fail over and seamless switching of masters for online maintenance. However, you can do far more. Tungsten Connector allows you to make better use of

Are you unsure of the steps needed to get your Continuent Tungsten cluster up-and-running? In this virtual course, we will teach you how to get from a single database server to a scalable cluster, or from a brittle MySQL replication system to a transparent, manageable Tungsten cluster. 

We will discuss the benefits of leveraging Continuent Tungsten clustering with MySQL, and walk you through the

High Availability (HA) ensures all important business information is available for your application even when there is no database failure. This includes:

How about when you are upgrading your database schema? What if you need to add memory to a database server or reconfigure/restart MySQL? If your apps want to read data from a MySQL slave, how can you be sure they are not reading stale data

La haute disponibilité, c’est garantir aux applications un accès permanent aux données, même en cas de panne. Permanent ? Même lorsque vous mettez à jour le schéma de vos bases ? Que vous ajoutez de la RAM sur un serveur ? Que vous reconfigurez ou redémarrez MySQL ?   

Comment lire les données depuis un nœud esclave avec une garantie que les données sont à jour, sans changement applicatif ?

Cross-site databases are the next challenge facing today's MySQL-based businesses. Continuent Tungsten provides multiple options for spreading data across sites, including primary/DR, multi-master, and system-of-record approaches. Join us to learn how Continuent Tungsten enables replication, failover, and routing of transactions between sites.

We cover the following topics:

Introduction to

If you’re a user of MySQL Workbench then you may have noticed a pocket knife icon appear in the top right hand corner – click on that and a terminal opens which gives you access to the MySQL utilities. In this post I’m focussing on the replication utilities but you can also refer to the full MySQL Utilities documentation.

What I’ll step through is how to uses these utilities to:

• Set up replication from a single master to multiple slaves
• Automatically detect the failure of the master and promote one of the slaves to be the new master
• Introduce the old master back into the topology as a new slave and then promote it to be the master again

Tutorial Video

Before going through the steps in detail here’s a demonstration of the replication utilities in action…

To get full …

After the GitHub MySQL Failover incident a lot of blogs/people have explained that fully automated failover might not be the most optimal solution.

Fully automated failover is indeed dangerous, and should  be avoided if possible. But a complete manual failover is also dangerous. A fully automated manually triggered failover is probably a better solution.

A synchronous replication solution is also not a complete solution. A split-brain situation is a good example of a failure which could happen. Of course most clusters have all kinds of safe guard to prevent that, but unfortunately also safe guards can fail.

Every failover/cluster should be considered broken unless:

1. You've tested the failover scripts and procedures
2. You've tested the failover scripts and procedures under normal load
3. You've tested the failover scripts and procedures under high load
…

As part of a recent engagement, I described the relative products to manage a MySQL pair (i.e. an Active/Passive MySQL masters configuration). This included the steps to undertake a controlled failover for supporting software maintenance using manual procedures. The upcoming Effective MySQL: Replication Techniques in Depth book details each step and all conditions to review over a dozen pages. While the steps are straightforward and generally well known, scripting this for your environment takes a certain amount of work to ensure your information is correct, and application connectivity loss is kept to a minimum.

In Continuent Tungsten (which I have just been reviewing these past few weeks), I achieved the same result with a single command.

$ echo "switch" | /opt/continuent/tungsten/tungsten-manager/bin/cctrl

In addition to all the …

With all of the new news coming out right now, it can be easy to miss or overlook some of the new features.

While there’s been a lot of talk about MySQL 5.6 Replication, I specifically wanted to mention the new ‘mysqlfailover’ and ‘mysqlrpladmin’ utilities.

These are two new MySQL replication utilities (results of the new Global Transaction Identifiers (GTIDs) in MySQL 5.6).

Let me quote the MySQL 5.6 Replication article for both of these utilities:

mysqlfailover

“Provides continuous monitoring of the replication topology, enabling failover to a slave in the event of an outage on the master.

The default behavior is to promote the most up-to-date slave, based on …