by Peter Zaitsev | Mar 3, 2015 | Insight for DBAs, MySQL, Percona Live
Talking with Percona Live attendees last year I heard a couple of common themes. First, people told me that there is a lot of great advanced content at Percona Live but there is not much for people just starting to learn the ropes with MySQL. Second, they would like...
by Ernie Souhrada | Sep 9, 2014 | Insight for DBAs, MySQL, Percona Software
A common migration path from standalone MySQL/Percona Server to a Percona XtraDB Cluster (PXC) environment involves some measure of time where one node in the new cluster has been configured as a slave of the production master that the cluster is slated to replace. In...
by Stephane Combaudon | Sep 5, 2014 | MySQL, Percona Services, Webinars
Thank you to all of you who attended my webinar last week about Global Transaction IDs (GTIDs), which were introduced in MySQL 5.6 to make the reconfiguration of replication straightforward. If you missed my webinar, you can still listen to the recording and download...
by Zardosht.Kasheff | Aug 7, 2014 | MySQL
This is the fourth post in a series of posts that explains Ark, a consensus algorithm we’ve developed for TokuMX and MongoDB to fix known issues in elections and failover. The tech report we released describes the algorithm in full detail. These posts are a layman’s...
by Zardosht.Kasheff | Jul 30, 2014 | MySQL
This is the third post in a series of posts that explains Ark, a consensus algorithm we’ve developed for TokuMX and MongoDB to fix known issues in elections and failover. The tech report we released last week describes the algorithm in full detail. These posts are a...
by Zardosht.Kasheff | Jul 25, 2014 | MySQL
This is the second post in a series of posts that explains Ark, a consensus algorithm we’ve developed for TokuMX and MongoDB to fix known issues in elections and failover. The tech report we released last week describes the algorithm in full detail. These posts are a...
by Zardosht.Kasheff | Jul 22, 2014 | MySQL
Last week, we introduced Ark, a consensus algorithm similar to Raft and Paxos we’ve developed for TokuMX and MongoDB. The purpose of Ark is to fix known issues in elections and failover. While the tech report detailing Ark explains everything formally, over the next...
by Zardosht.Kasheff | Jul 18, 2014 | MySQL
Most of the time, our blog posts explain what’s great about the MongoDB improvements we’ve already shipped in TokuMX. Sometimes, though, it’s fun to talk about what’s coming soon, especially when user feedback would really help get the feature right. In my next...
by Michael Coburn | Jul 2, 2014 | Cloud, Insight for DBAs, MySQL
I recently had an opportunity to migrate a customer from a physical server into Amazon’s RDS environment. In this particular case the customers’ platform makes extensive use of MySQL triggers and views. I came across two significant issues that prevented...
by Dave Rosenlund | Jun 5, 2014 | MySQL
MongoDB replication has a lot of great features including crash safety, automatic failover and parallel slave replication. Although MongoDB’s replication is impressive in many ways, TokuMX™ replication internals are purposely designed differently. Register Now!...
by Zardosht.Kasheff | Jun 5, 2014 | MySQL
Over several posts, I’ve explained the differences between TokuMX replication and MongoDB replication, and why they are completely incompatible. In this (belated) post, I explain one last difference: the oplog format for operations. Specifically, TokuMX and MongoDB...
by Stephane Combaudon | May 19, 2014 | Insight for DBAs, MySQL
I have previously written about the new replication protocol that comes with GTIDs in MySQL 5.6. Because of this new replication protocol, you can inadvertently create errant transactions that may turn any failover to a nightmare. Let’s see the problems and the...
by Martin Arrieta | May 15, 2014 | Insight for DBAs, MySQL
In our previous post, we introduced the MySQL Fabric utility and said we would dig deeper into it. This post is the first part of our test of MySQL Fabric’s High Availability (HA) functionality. Today, we’ll review MySQL Fabric’s HA concepts, and...
by Stephane Combaudon | May 9, 2014 | Insight for DBAs, MySQL
One of the MySQL 5.6 features many people are interested in is Global Transactions IDs (GTIDs). This is for a good reason: Reconnecting a slave to a new master has always been a challenge while it is so trivial when GTIDs are enabled. However, using GTIDs is not only...
by Zardosht.Kasheff | Apr 15, 2014 | MySQL
As I’ve mentioned in previous posts, TokuMX replication differs quite a bit from MongoDB’s replication. The differences are large enough such that we’ve completely redone some of MongoDB’s existing algorithms. One such area is how secondaries apply oplog data from a...
by Zardosht.Kasheff | Apr 2, 2014 | MySQL
In a post last week, I described the difference in concurrency behavior between MongoDB’s oplog and TokuMX’s oplog. In short, here are the key differences: MongoDB protects access to the oplog with a database level reader/writer lock, whereas TokuMX does not. TokuMX...
by Zardosht.Kasheff | Mar 28, 2014 | MySQL
In my last post, I describe the differences between a TokuMX oplog entry and a MongoDB oplog entry. One reason why the entries are so different is that TokuMX supports multi-statement and multi-document transactions. In this post, I want to elaborate on why...
by Zardosht.Kasheff | Mar 26, 2014 | MySQL
by Zardosht.Kasheff | Mar 24, 2014 | MySQL
MongoDB replication has some great features. As I discussed in my last post, MongoDB’s crash safety design is very elegant. In addition to that, MongoDB has automatic failover, parallel slave replication, and prefetch threads on secondaries. The latter, as Mark...
by Zardosht.Kasheff | Mar 18, 2014 | MySQL
At an extremely high level, replication in MongoDB and MySQL are similar. Both databases have exactly one machine, the primary (or master), that accepts writes from clients. With a single transaction (or atomic operation, in MongoDB’s case), the tables and oplog (or...
