Showing entries 31 to 40 of 191
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: scalability (reset)
No tools to reconcile MySQL with two masters

Here’s the last nail in the coffin. We hope this convinces you not to write to multiple masters with MySQL replication. Reason 10 – No tools to reconcile inconsistent masters For all the endless reasons we’ve already outlined MySQL replication is prone to failure. We know it’s going to happen, you now know too. When [...]

Temp tables can break replication

If you’re not convinced yet that writing to dual masters is a bad idea, we have a couple more reasons. 9. Temp tables break replication after restart MySQL’s replication is sensitive to temporary tables. You shouldn’t use them. If your queries create them to work against, and a node crashes, the temp tables will be [...]

Crashed nodes corrupt your MySQL cluster

Read the original article at Crashed nodes corrupt your MySQL cluster

Writing to two masters is like walking around with a loaded shotgun. Eventually one of your instances will fail and when it does, replications position & synchronization information could easily become corrupt! Reason 8 – Crashed nodes cause big problems MySQL instances, unfortunately can crash. When that happens, they don’t always sync the replication position [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. MySQL Cluster In The Cloud – Managers Guide
[Read more]
Transaction isolation breaks when writing two masters

Read the original article at Transaction isolation breaks when writing two masters

Continuing our discussion of multi-master replication, we hit on five more reasons why writing to two masters aka active-active replication is very dangerous. Click through to the end for multi-master solutions that work with MySQL. Reason 6 – You lose transaction isolation This may sound like a theoretical point to some. But hopefully we can [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. MySQL needs single master to check data integrity
[Read more]
Active-active replication reduces operational flexibility

Read the original article at Active-active replication reduces operational flexibility

Among the myriad data integrity and corruption risks associated with active-active replication, you also lose out on configurability and operational flexibility. Reason 7 – Can’t add nodes easily The often touted solution to use auto_increment_increment and auto_increment_offset fixes you to a given setup forever. You can set it up with a discrete two nodes, all [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. 10 reaons active-active is hard and how to solve it
[Read more]
How to make MySQL multi-master work for you

Read the original article at How to make MySQL multi-master work for you

Coming soon! Want more? Grab our Scalable Startups monthly for more tips and special content. Here’s a sample Related posts:Transaction isolation breaks when writing two masters MySQL requires an authoritative master to build slaves MySQL needs single master to check data integrity A master isn’t born but made Why does MySQL replication fail?

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. Transaction isolation breaks when writing two masters
[Read more]
MySQL needs single master to check data integrity

Read the original article at MySQL needs single master to check data integrity

MySQL slaves can drift out of sync. Many of our clients are surprised to find some data differences in their replication topology, once we do some checking and sniffing around. Such checks require a single reliable or authoritative master to compare against. Click through to the end for multi-master solutions that work with MySQL. Reason [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. MySQL requires an authoritative master to build slaves
[Read more]
MySQL requires an authoritative master to build slaves

Read the original article at MySQL requires an authoritative master to build slaves

In MySQL database operations, you often need to rebuild slaves. They fail for a lot of different reasons, fall out of sync or crash. When this happens you may find you need to reclone and start fresh. This is normally done by finding your authoritative master database, and doing a hotbackup. Click through to the [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. Limitations of MySQL row-based replication
[Read more]
Limitations of MySQL row-based replication

Read the original article at Limitations of MySQL row-based replication

MySQL offers a few different options for how you perform replication. Statement-based has been around a lot longer, and though it has some troublesome characteristics they’re known well and can be managed. What’s more it supports online schema changes with multi-master active-passive setup. We recommend this solution. Row-based replication is newer. It attempts to address [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. Why does MySQL replication fail?
[Read more]
Why does MySQL replication fail?

Read the original article at Why does MySQL replication fail?

When considering active-active multi-master, you must consider it’s foundation technology. Although MySQL replication is straightforward to setup, it can fail in a myriad of ways. Most of those are known and well understood. We can solve them only if we use the technology in the standard way. Click through to the end for multi-master solutions [...]

For more articles like these go to Sean Hull's Scalable Startups

Related posts:

  1. 5 Ways to fortify MySQL replication
  2. Easy …
[Read more]
Showing entries 31 to 40 of 191
« 10 Newer Entries | 10 Older Entries »