Comments on: MySQL Cluster, is it worth it? http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/ noise from a mozilla network engineer Thu, 08 May 2008 18:34:52 +0000 http://wordpress.org/?v=wordpress-mu-1.2.5 By: Archon810 http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-5276 Archon810 Tue, 06 Nov 2007 02:30:52 +0000 http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-5276 s/Mozilla what/Mozilla for/ s/Mozilla what/Mozilla for/

]]> By: Archon810 http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-5271 Archon810 Tue, 06 Nov 2007 01:11:23 +0000 http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-5271 Hi mrz. Bret Reckard pointed me to this post after finding out that somewhere in the depths of beer planet I was writing a MySQL cluster setup guide. I'll try to answer some of your questions in the post, but feel free to read this modest article: http://beerpla.net/2007/11/05/setting-up-a-mysql-cluster/. 1 and 2. I think that in general, if you do a lot of CPU intensive selects, you should add more SQL nodes. If, however, you do a lot of inserts/updates, you should consider adding more data nodes. Another important point is to try to isolate the cluster and put it onto its own switch and subnet as network latency is a big factor of how fast the cluster is going to perform. 3. The cluster is fully A.C.I.D. compliant, unlike replication, where a slave can fall off and stupidly get behind. It fully supports transactions, which I'm a big fan of. If you're having problems with transactions deadlocking, consider tweaking the transaction related cluster properties. 4. is answered in the guide. In short, nothing breaks, but no new nodes can (re)join the cluster if the management node isn't up. Let me know if there is anything in the guide that can be more clear, or if there are any mistakes or omissions. Respect to Mozilla what everything you're doing. Archon810. Hi mrz. Bret Reckard pointed me to this post after finding out that somewhere in the depths of beer planet I was writing a MySQL cluster setup guide.

I’ll try to answer some of your questions in the post, but feel free to read this modest article: http://beerpla.net/2007/11/05/setting-up-a-mysql-cluster/.

1 and 2. I think that in general, if you do a lot of CPU intensive selects, you should add more SQL nodes. If, however, you do a lot of inserts/updates, you should consider adding more data nodes. Another important point is to try to isolate the cluster and put it onto its own switch and subnet as network latency is a big factor of how fast the cluster is going to perform.

3. The cluster is fully A.C.I.D. compliant, unlike replication, where a slave can fall off and stupidly get behind. It fully supports transactions, which I’m a big fan of. If you’re having problems with transactions deadlocking, consider tweaking the transaction related cluster properties.

4. is answered in the guide. In short, nothing breaks, but no new nodes can (re)join the cluster if the management node isn’t up.

Let me know if there is anything in the guide that can be more clear, or if there are any mistakes or omissions.

Respect to Mozilla what everything you’re doing.
Archon810.

]]> By: Callek http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-4408 Callek Tue, 23 Oct 2007 00:25:11 +0000 http://blog.mozilla.com/mrz/2007/10/22/mysql-cluster-is-it-worth-it/#comment-4408 mrz, I'd be interested in what you find out about this, whether you update this post, make a new post, or simply add a comment (if you add a comment, I would appreciate a ping so I can know to read it). Thanks in advance. ~Justin Wood (Callek) mrz, I’d be interested in what you find out about this, whether you update this post, make a new post, or simply add a comment (if you add a comment, I would appreciate a ping so I can know to read it).

Thanks in advance.
~Justin Wood (Callek)

]]>