On TokuMX (and MongoDB) Replication and Transactions
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...
View ArticleOn TokuMX Oplog, Tailable Cursors, and Concurrency
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...
View ArticleHow TokuMX Secondaries Work in Replication
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...
View ArticleClik here to view.
Why TokuMX Changed MongoDB’s Oplog Format for Operations
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:...
View ArticleClik here to view.
June 11 Webinar: Comparing MongoDB and TokuMX Replication
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...
View ArticleIntroducing Ark: A Consensus Algorithm For TokuMX and MongoDB
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...
View ArticleExplaining Ark Part 1: The Basics
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...
View ArticleExplaining Ark Part 2: How Elections and Failover Currently Work
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...
View ArticleExplaining Ark Part 3: Why Data May Be Lost on a Failover
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...
View ArticleExplaining Ark Part 4: Fixing Majority Write Concern
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...
View Article
