The MySQL team at Oracle are excited to announce the immediate availability of the second MySQL Cluster 7.3 Development Milestone Release (DMR). Some might call MySQL Cluster 7.3 "the foreign keys release" - and sure enough it is a major engineering achievement to build a distributed database that enforces referential integrity across a shared-nothing cluster, while maintaining ACID compliance and cross-shard JOINs. But MySQL Cluster 7.3 is so much more as well. The design focus has been on enabling developer agility - making it simpler and faster than ever to enhance new services with a highly scalable, fault tolerant, real-time database - with minimum development or operational effort.
Apr
17
2013
Apr
17
2013
You should probably read Marc Alff’s post about configuring Performance Schema in MySQL 5.6.
We wrote another guide, how to start using user/table/index statistics first introduced in Google patch, now part of various MySQL branches and forks:
- Start MySQL
Apr
16
2013
From time to time I will observe servers wasting lots of CPU when
doing batch row operations. In perf top it will look
like this:
8.24% mysqld [.] Arg_comparator::compare_int_unsigned() 7.17% mysqld [.] Item_cond_and::val_int() 4.37% mysqld [.] Item_field::val_int() 4.37% mysqld [.] Item_cond_or::val_int() 2.90% mysqld [.] MYSQLparse(void*) 2.64% mysqld [.] Item::val_bool()
Essentially if you construct queries like (a=1 AND b=2) OR
(a=3 AND b=4) ..., at large enough batch size evaluating
the WHERE will become far more expensive than anything else (yes,
more expensive than decompressing rows or doing all the InnoDB
magic and what not).
MySQL has awesome syntax that makes certain batch lookups much faster: WHERE a IN (1,2,3). It constructs a tree that then each row can be compared against and one does not have to iterate through lists of predicates to check whether the row returned by batch index lookups …
[Read more]
Apr
16
2013
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:
[Read more]
Apr
16
2013
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:
[Read more]
Apr
16
2013
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:
[Read more]
Apr
16
2013
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:
[Read more]
Apr
16
2013
Read the original article at 10 reaons active-active is hard and how to solve it
Multi-master replication provides redundant copies of your most important business assets. What’s more it allows applications to scale out, which is perfect for cloud hosting solutions like Amazon Web Services. But when you decide you need to scale your write capacity, you may be considering active-active setup. This is dangerous, messy and prone to failure. [...]
For more articles like these go to Sean Hull's Scalable Startups
Related posts:
[Read more]
Apr
16
2013
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:
[Read more]
Apr
16
2013
I just got invited to this: MySQL Studio Photos @ Percona Live MySQL. I immediately signed up on the Indiegogo page for MySQL Portrait Photographs. I’m going and I’m happy to see the photographer again.
Julian Cash is an incredibly talented photographer (check out his portfolio) who for some years did some light painting at the MySQL Conference. He also did some wide angle photos. Overall my portrait photo is basically shot by Julian, and I can’t wait to get an additional one. Julian portrays Human Creativity, and he’s also an incredibly nice person. He will bring out the best in you.
If …
[Read more]