EmergencyEMERGENCY? Get 24/7 Help Now!

Using MySQL 5.6 Global Transaction IDs (GTIDs) in production: Q&A

 | September 5, 2014 |  Posted In: MySQL, Percona MySQL Consulting, Technical 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 the sides (free). We had a lot of questions during the […]

Read More

Explaining Ark Part 4: Fixing Majority Write Concern

 | August 7, 2014 |  Posted In: Tokutek, TokuView

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 explanation. This post assumes the reader is familiar with […]

Read More

Explaining Ark Part 1: The Basics

 | July 22, 2014 |  Posted In: Tokutek, TokuView

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 few blog posts, I will go over Ark in layman’s terms. […]

Read More

Using MySQL triggers and views in Amazon RDS

 | July 2, 2014 |  Posted In: Cloud and MySQL, Cloud and NoSQL, 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 me from following Amazon’s documentation, which basically states “use mysqldump” but doesn’t call out a […]

Read More

June 11 Webinar: Comparing MongoDB and TokuMX Replication

 | June 5, 2014 |  Posted In: Tokutek, TokuView

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! SPEAKER: Zardosht Kasheff, Sr. Engineer DATE: Wednesday, June 11th TIME: 1pm EDT/10am PDT TokuMX is built on Fractal Tree® technology, unlike […]

Read More

Why TokuMX Changed MongoDB’s Oplog Format for Operations

 | June 5, 2014 |  Posted In: Tokutek, TokuView

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 log updates and deletes differently. Suppose we have a collection foo, with the following element:

We perform […]

Read More

Errant transactions: Major hurdle for GTID-based failover in MySQL 5.6

 | May 19, 2014 |  Posted In: High-availability, 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 potential solutions. In short Errant transactions may cause all kinds of data corruption/replication […]

Read More