Showing entries 51 to 60 of 215
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: scalability (reset)
The Most Important AWS Feature for Performance and Scalability

Join 6100 others and follow Sean Hull on twitter @hullsean. The Foundation of Speed All servers use disk to store files. Operating system libraries, webserver & application code, and most importantly databases all use disk constantly. So disk speed is crucial to server speed. [mytweetlinks] [quote] Disk speed is crucial for MySQL databases. It has [...]

Five More Things Deadly to Scalability

Read the original article at Five More Things Deadly to Scalability

Join 6000 others and follow Sean Hull on twitter @hullsean. 1. Slow Disk I/O – RAID 5 – Multi-tenant EBS Disk is the grounding of all your servers, and the base of their performance. True with larger and larger main memory, much is available in cache, a server still needs to constantly read from disk [...]

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

Related posts:

  1. Mobile Scalability – What is it and why is it important?
[Read more]
Make MySQL clustering work for you

We’ve told you all about MySQL mult-master replication’s limitations. If you write to two masters it is bound to fail for myriad reasons. Now what? Do what the pros do that’s what. A. Don’t write to both masters Using multi-master replication works great as long as you do so in active-passive mode. Never write to [...]

Scaling Drupal on Multiple Servers with Galera Cluster for MySQL

April 26, 2013 By Severalnines

This post shows you how to move from a single instance Drupal/MySQL to a multi-server environment. A well designed multi-server deployment not only allows Drupal to scale, but will also enhance redundancy by removing single points of failure. Components used are Apache, PHP, csync2, lsyncd, Keepalived, HAproxy, MySQL Galera Cluster and ClusterControl.

read more

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]
Showing entries 51 to 60 of 215
« 10 Newer Entries | 10 Older Entries »