Charles,

first, my opinion is that if you are paying Oracle you should get answers
from them about this, and then of course is good to have a second opinion
here.

Related to your specific question you should specify what you mean with
'clustering' which is a generic term,
if with it you mean "MySQL Cluster" product then you have to know that this
implementation of database cluster is based on a specific storage engine
called Network DataBase (NDB), so you can't choose another engine for it.
The default storage engine in the SQL nodes of a MySQL Cluster can be any
storage engine and whether it be MyISAM, InnoDB, NDB and it's a design
decision, but only NDB tables will benefit from the clustering capabilities.

I hope I got your question right and that this shed a bit more light for
you.

Cheers

Claudio

2012/4/28 Brown, Charles <cbr...@bmi.com>

> The question is, is it advisable to change the default engine of a cluster
> setting to Myisam? Does anyone have an opinion or experience on this issue?
> Do I have choice when it comes to clustering on which type engine supports
> clustering.
> Thanks
>
>
>
> -----Original Message-----
> From: Reindl Harald [mailto:h.rei...@thelounge.net]
> Sent: Saturday, April 28, 2012 3:01 AM
> To: mysql@lists.mysql.com
> Subject: Re: engine is now innoDB instead of MyISAM.
>
>
>
> Am 28.04.2012 09:00, schrieb Brown:
> > We recently switched from MySQL community to Mysql clustered using
> Oracle supported MySQl. The problem is, during our testing phase, we
> observed the default engine is now innoDB instead of MyISAM. Any thoughts
> on that? We're not getting the performance that we expected - any thoughts
> or advices out there will be greatly appreciated.
>
> my.cnf: default-storage-engine = myisam
>
> you cann not compare MyISAm and InnoDB for the same workloads that's why
> my.cnf exists and we usually define each known setting to prevent chnages
> in the behavior of applications by software-updates
>
> the same for "php.ini"
>
> ********************************************
> This message is intended only for the use of the Addressee and
> may contain information that is PRIVILEGED and CONFIDENTIAL.
>
> If you are not the intended recipient, you are hereby notified
> that any dissemination of this communication is strictly prohibited.
>
> If you have received this communication in error, please erase
> all copies of the message and its attachments and notify us
> immediately.
>
> Thank you.
> ********************************************
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql
>
>


-- 
Claudio

Reply via email to