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: | Simon Garner (sgar...@expio.co.nz) |
| Date: | 06/29/2005 10:23:27 PM |
| List: | com.mysql.lists.cluster |
On 30/06/2005 6:41 a.m., joseph kacmarcik wrote:
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.
We do something similar. While you can mix MyISAM, InnoDB and NDB tables in one database, and you can use --replicate-wild-do-table to replicate only the non-clustered tables, we found this to be non-ideal as you then either have to name your tables with some prefix to indicate if they are clustered or not, or manually update your replicate-wild-do-table configuration every time you add or remove a table.
What would be nice for the future would be an option like --replicate-do-engine where you could specify table types which would or would not be replicated, so e.g. NDB tables could be excluded from replication without specifying the actual table names.
-Simon