4 ms·
I'm still trying to find time for a writeup of how we use MySQL Galera, but I'll take this chance to note again that any big MySQL houses out there should reall
by druiid 14y ago
I'm still trying to find time for a writeup of how we use MySQL Galera, but I'll take this chance to note again that any big MySQL houses out there should really take a look at it and see if it will work within your environment. Basically it's a true multi-master MySQL environment with shared-nothing (kind of like MySQL cluster). We've run into our share of bugs, be we're perhaps more of an edge case. We create a TON of temporary tables and were encountering a bug which was eating up memory slowly. That has been fixed for a couple releases now and everything has been groovy.
Basically though, the cluster takes care of ejecting bad slaves so you'll never need to worry about the replication status, etc.
Oh, and feel free to contact me through profile if you have any questions about it. We have a good long use of it now and pretty much know about most/all of the things to watch out for.
- falcolas 14y agoThe biggest problem with Galera cluster right now is that you can't have large, long lived transactions. Due to the way that the non-write nodes verify data consistency, large transactions can cause some serious slowdown issues for the entire cluster.
- druiid 14y agoTrue and that would certainly qualify under an 'edge case' scenario, although if you increase the number of threads I believe it should mitigate this particular issue somewhat (more threads open to do other applies at the same time). Obviously if you need to have dozens of long writes at the same time this isn't solved for.
- SergeyHack 14y agoIt would be really interesting to read your writeup on MySQL Galera usage.