NDB! NDB! The storage engine for me!

Today I set up a mysqld connected to my not-quite-HA cluster at home here to replicate from my MythTV database into cluster. The idea behind this is to eat an increasing amount of my own dogfood around the house.

To do this, I also set up the MySQL Instance Manager to manage the now multiple instances of MySQL Servers on a box here. I found it a pain to do, it should be a lot simpler, but isn’t. At least now things are going okay…. but the feature wish list I have is rather long (perhaps I should hack some stuff up in this “spare time” i’ve been hearing so much about).

I’m also about 10 minutes (or however long the build takes) off moving one of the data nodes off the machine so it will be a real 2 node system (but I still have to move the management server to a third machine to have any real HA… and I have a PowerPC machine marked for that, I just have to await some patches to make it work :)

Currently though, my Gallery is being served off this. There are so many more photos I should add, I just haven’t come up with a decent way to interface f-spot and Gallery together – especially when I go back and retouch, delete or tag photos.

4 thoughts on “NDB! NDB! The storage engine for me!

  1. ??
    Database Error
    An error has occurred while interacting with the database

    Maybe need some setting. I found strange behavior, when queries to NDB became slower and slower even if using index even if data was the same.

  2. ahh… I’ve been screwing with it a lot too, so probably caught it when it was down… i’ll go fix it :)

  3. Stewart,

    You say you are running multiple mysql instances on the same box and clustering them? What sort of hardware? How is the performance of NDB with multiple instances on the same box vs. fast network of instances on their own boxes?

    I’m architecting my company’s db setup and am trying to figure out what the fastest, reliable replication/clustering setup would be

  4. Better to have each ndbd on its own machine… unless you have multiple CPUs (not really recommended).

    Multiple mysqld isn’t really needed though, unless you’re doing strange stuff like me – wanting to have several databases being replicated into the same cluster.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.