EmergencyEMERGENCY? Get 24/7 Help Now!

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

Why a Partitioned Collection Cannot Be Sharded

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

In TokuMX 1.5, we introduced partitioned collections for non-sharded clusters. That is, one can have a partitioned collection in a replica set, but one cannot shard a partitioned collection. In this post, I explain why. As I mentioned here, partitioned collections are useful for time-series data where we would like to keep a rolling period […]

Read More

Best Practices for Partitioned Collections and Tables in TokuDB and TokuMX

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

In my last post, I gave a technical explanation of the performance characteristics of partitioned collections in TokuMX 1.5 (which is right around the corner) and partitioned tables in relational databases. Given those performance characteristics, in this post, I will present some best practices when using this feature in TokuMX or TokuDB. Note that these […]

Read More

Understanding the Performance Characteristics of Partitioned Collections

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

In TokuMX 1.5 that is right around the corner, the big feature will be partitioned collections. This feature is similar to partitioned tables in Oracle, MySQL, SQL Server, and Postgres. A question many have is “why should I use partitioned tables?” In short, it’s complicated. The answer depends on your workload, your schema, and your […]

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