Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

this is my first post here, so go easy on me.

I'm trying to rebuild my data architecture (which is currently a set of one primary MySQL server and a redundant fallback; the tables are primarily InnoDB for transactional features). This has worked well in the past, but with recent increases in traffic, it's not holding up very well.

At first I was considering adding a 'memory' cache table to speed things up, but I'd prefer something with transactions. So I've been looking into setting up a MySQL Cluster, but the documentation is a lot to take in, and I've now gotten myself very confused. Here's what I hope to accomplish:

I'd still like to have two mysqld machines, but I'd like to add two or three ndb nodes, and have the mysqld machines double as ndm-mgmd.

Is this a practical setup? How do I go about configuring this? If anyone knows of helpful examples or guides, I'd be pleased as punch (I've been searching, and each guide I stumble upon is twice as confusing as the last).

share|improve this question

A great place to get started with MySQL Cluster are these Quick Start guides:

In terms of hardware profile, commodity servers are just fine - take a look at some of the recent benchmarks - 4.3m QPS across 8 x Intel dual socket servers with 24GB RAM:

Hope this helps. Let us know how you get along, and also go to the MySQL Cluster forum for direct access to engineering team:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.