Re: engine is now innoDB instead of MyISAM.

2012-04-29 Thread Brown, Charles
Well said. Thanks so much. Sent from my iPhone On Apr 29, 2012, at 8:02 AM, "Reindl Harald" wrote: > > > Am 29.04.2012 14:50, schrieb Brown: >> is a complain I received from one of my developer that after following our >> MySQL >> Cluster migration, tables are now defaulting to innodb (how

RE: engine is now innoDB instead of MyISAM.

2012-04-29 Thread Claudio Nanni
Charles, I think going back to MyISAM as default is a good idea. All you have to do is: Export all databases .Shutdown the cluster MySQL .Add one parameter to your old my.cnf , default-storage-engine=myisam .add cluster specific parameters to your my.cnf , they should be a couple .Put back your my

Re: engine is now innoDB instead of MyISAM.

2012-04-29 Thread Reindl Harald
Am 29.04.2012 14:50, schrieb Brown: > is a complain I received from one of my developer that after following our > MySQL > Cluster migration, tables are now defaulting to innodb (how can he tell) as already said: the builtin default has changed an you have to configure MyISAM as default your

RE: engine is now innoDB instead of MyISAM.

2012-04-29 Thread Brown, Charles
Hello Claudio, Thanks for quick response and the whitepaper. What precipitated my research and questions is a complain I received from one of my developer that after following our MySQL Cluster migration, tables are now defaulting to innodb ( how can he tell) and performance is poor. I'm very

Re: engine is now innoDB instead of MyISAM.

2012-04-29 Thread Claudio Nanni
Charles, the pleasure is all mine in meeting such a kind person as you are. To reply to your question, I would recommend to read frst a basic document about MySQL Cluster, like the whitepaper (http://kae.li/iiisv) so that you have an overview of the infrastructure. Consider that only the SQL nod