RE: questions about ndb - Jonathan Miller - com.mysql.lists.cluster

6 messages in com.mysql.lists.clusterRE: questions about ndb

From	Sent On	Attachments
joseph kacmarcik	29 Jun 2005 11:41
Jonathan Miller	29 Jun 2005 13:09
Jonathan Miller	29 Jun 2005 13:45
Stewart Smith	29 Jun 2005 22:08
Simon Garner	29 Jun 2005 22:23
Simon Garner	29 Jun 2005 22:29

Subject:	RE: questions about ndb
From:	Jonathan Miller (jmil...@mysql.com)
Date:	06/29/2005 01:45:12 PM
List:	com.mysql.lists.cluster

5) is it supported to do join queries of ndb tables and myisam or innodb tables?

mysql> create table t1 (c1 int, c2 char(8), PRIMARY KEY (c1))engine=innodb; Query OK, 0 rows affected (0.02 sec)

mysql> create table t2 (c1 int, c2 char(8), PRIMARY KEY (c1))engine=ndb; Query OK, 0 rows affected (3.22 sec)

Insert into t1 values (1,"test"),(2,"ABC"),(3,"work"); Insert into t2 values (1,"test"),(2,"ABC"),(3,"work");

Select t1.c2 from t1 join t2 where t1.c1 = t2.c1;

Seems to work fine.

Thanks. JBM

-----Original Message----- From: joseph kacmarcik [mailto:joe-...@earth.care2.com] Sent: Wednesday, June 29, 2005 1:42 PM To: clus...@lists.mysql.com Subject: questions about ndb

hi list!

i have a few questions about NDB, which i'm unable to find definitive answers on in the list archives, and other places.

1) the way i understand NDB is that, to an sql nodes, it's just another engine (like innodb or myisam). is it supported to have an sql node act as a master for n slaves, and have ndb tables in the same replicated db? the ndb tables would not be replicated, but the slaves would have the ndb engine, and therefore should be able to act as replicating slaves, as well as sql nodes for the ndb cluster. i'll have a database named 'tables' with myisam tables (replicated), and ndb tables (not replicated). i want to use the same database name.

2) the way i understand the sql node concept is that read queries are executed on the machine the query is directed to, and not on the storage nodes or management node. i could have a series of sql nodes behind a load-balancer, and throw read queries at the LB, not caring where they go.

2b) i've read of slow read query performance, but wouldn't this be alleviated by a fast sql node (or optimized query or adding an index, etc)?

3) with today's fast ram, is the current bottleneck for fast writes the network connections over which the sql node(s) is connected to the storage nodes? ie: i can write much faster to a ramdisk than i can to a ramdisk over Gbit ethernet.

4) is downtime required to expand the ndb storage size? is it as simple as adding storage nodes, modifying the DataMemory (and IndexMemory), adding [NDBD] entries and restarting the management node? i'll always have backups, but are there risks in taking down the management node while sql nodes are accepting queries?

this is all for now. information greatly appreciated. joe