Showing entries 1 to 5
Displaying posts with tag: multi-master replication (reset)
Taking Full Advantage of Galera Multi-Master Webinar – Dec 13th

Description

 

This webinar will be the second in our series on best practices to follow when using Galera Cluster.

In this part, we will discuss important topics related to multi-master setups:
* Practical considerations when using Galera in a multi-master setup
* Evaluating the characteristics of your database workload
* Preparing your application for multi-master
* Detecting and dealing with transaction conflicts

This is a webinar presented by Codership, the developers and experts of Galera Cluster.

DATE AND TIME FOR USA:  Tuesday, 9-10 AM PST (Pacific ), 13th of December

REGISTER TO USA WEBINAR WITH THIS LINK 

 

DATE AND TIME FOR …

[Read more]
View Galera Cluster Best Practices Webinar Replay Part One!

Codership’s Galera Cluster Best Practices Webinar for MySQL DBAs and DevOps Part One is now available to watch here

MySQL Cluster 7.4 is GA!

The General Availability of MySQL Cluster 7.4 has just been announced by Oracle.

The MySQL team at Oracle are excited to announce the General Availability of MySQL Cluster 7.4, ready for production workloads.

MySQL Cluster 7.4.4 can be downloaded from mysql.com and the release notes viewed in the MySQL docs.

Figure 1 provides a summary of the enhancements delivered in this release:

  • Performance
    • 200M NoSQL Reads/Sec
    • 2.5M SQL Ops/Sec
    • 50% …
[Read more]
Auto failover of mysql master in mysql multi-master multi-slave cluster

This post is an extension to my earlier posts about multi master replication cluster multi master replication in mysql and mysql multi master replication act II The problem I had encountered and discussed was with automatic failover. What happens when the master goes down? How can either a slave or another master be promoted to become the master? Once the settings are done on all the mysql dbs

Mysql HA solutions

Lets see what HA solutions can be designed in mysql and where are they suited.

1. Single master - single slave.

M(RW)|S(R) A simple master slave solution can be used for a small site - where all the inserts go into the master and some (non-critical) requests are served from the slave. In case if the master crashes, the slave can be simply promoted as the master - once it has replicated the "

Showing entries 1 to 5