EmergencyEMERGENCY? Get 24/7 Help Now!

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: 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

High Availability with MySQL Fabric: Part I

and  | May 15, 2014 |  Posted In: High-availability, 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 then walk you through the setup of a 3-node cluster with one Primary and two […]

Read More

How TokuMX Secondaries Work in Replication

 | April 15, 2014 |  Posted In: Tokutek, TokuView

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 primary. In this post, I’ll explain how. In designing how secondaries apply oplog data, […]

Read More

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below and we’ll send you an update every Friday at 1pm ET.

No, thank you. Please do not ask me again.