7 messages in com.mysql.lists.clusterRE: 3 short questions
FromSent OnAttachments
Nick Hoffman20 Jun 2006 03:43 
Black, Ben20 Jun 2006 06:25 
Arne Hueggenberg21 Jun 2006 06:33 
Nick Hoffman21 Jun 2006 17:20 
Nick Hoffman21 Jun 2006 17:24 
Stewart Smith21 Jun 2006 21:27 
Jonathan Miller22 Jun 2006 05:28 
Subject:RE: 3 short questions
From:Black, Ben (Ben.@garmin.com)
Date:06/20/2006 06:25:29 AM
List:com.mysql.lists.cluster

-----Original Message----- From: Nick Hoffman [mailto:nick@altcall.com] Sent: Tuesday, June 20, 2006 5:44 AM To: clus@lists.mysql.com Subject: 3 short questions

Hi guys, I've been doing a lot of research on MySQL Cluster and have a couple of questions. If you wouldn't mind fielding these, I'd really appreciate it.

1) What is arbitration? I've seen it mentioned several times with respect to MGM node failure.

2) Which of the following combinations of nodes can run on a single physical machine?: 1) Storage and MGM node 2) Storage and SQL node 3) Storage and MGM and SQL node 4) SQL and MGM Node

For dev/test, I have run all 3 on a single server. This is not recommended for production. Currently for production I have 4 servers that run both ndb and mysql. As usage increases I plan to move the mysql nodes to their own server. I put MGM on an existing server since it doesn't use a lot of resources.

3) Do all tables stored in a MySQL Cluster storage node need to use the NDB engine? I've read posts saying that other engines can be used (Eg: InnoDB), but have a feeling they're mistaken.

This is somewhat true. All the tables stored in an ndb node must be ndb, but you may use other engines on the mysql nodes. We currently do this. Tables using ndb are for customer transactions and MyISAM tables are used for data that is entered internally and is static to the website. You can also join ndb tables to MyISAM tables in queries. You will need to use replication or some other means to keep all the non-ndb tables syncronized if you have more than one mysql node.

If you receive this email by mistake, please notify us and do not make any use of the email. We do not waive any privilege, confidentiality or copyright associated with it.