cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhinandan Prateek <abhinandan.prat...@shapeblue.com>
Subject Re: Few tables in cloudstack schema use MyISAM engine
Date Wed, 31 Aug 2016 03:37:14 GMT
Thanks, Koushik.

Have created a PR to make the engine type consistent for all tables.
InnoDB allows for replication, that is all the more reason that we change the engine type
of these few tables to InnoDB.

Regards,
-abhi

PR: https://github.com/apache/cloudstack/pull/1667


From: Koushik Das <koushik.das@accelerite.com<mailto:koushik.das@accelerite.com>>
Date: Tuesday, 30 August 2016 at 5:25 PM
To: Abhinandan Prateek <abhinandan.prateek@shapeblue.com<mailto:abhinandan.prateek@shapeblue.com>>,
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
Cc: Rajani Karuturi <rajani@apache.org<mailto:rajani@apache.org>>, Raja Pullela
<raja.pullela@accelerite.com<mailto:raja.pullela@accelerite.com>>
Subject: Re: Few tables in cloudstack schema use MyISAM engine

I cannot think of any. Most probably in all cases the engine was not explicitly specified
and the default got used. As per below default was myisam before mysql 5.5.5.
https://dev.mysql.com/doc/refman/5.5/en/storage-engine-setting.html

Thanks,
Koushik
From: Abhinandan Prateek <abhinandan.prateek@shapeblue.com<mailto:abhinandan.prateek@shapeblue.com>>
Date: Tuesday, 30 August 2016 at 4:23 PM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
Cc: Rajani Karuturi <rajani@apache.org<mailto:rajani@apache.org>>, Raja Pullela
<raja.pullela@accelerite.com<mailto:raja.pullela@accelerite.com>>, Koushik Das
<koushik.das@accelerite.com<mailto:koushik.das@accelerite.com>>
Subject: Few tables in cloudstack schema use MyISAM engine

Hi,

   Was there any specific reason that some tables in cloudstack schema use MyISAM engine.
I know of “ quota_account” that I created and put in the diff table type unknowingly.
I assume such is the case with other such tables – load_balancer_cert_map, monitoring_services,
nic_ip_alias, sslcerts.

Filed a ticket here to get this fixed or reason for not fixing it captured.

Regards,
-abhi

abhinandan.prateek@shapeblue.com<mailto:abhinandan.prateek@shapeblue.com>
www.shapeblue.com
@shapeblue




DISCLAIMER ========== This e-mail may contain privileged and confidential information which
is the property of Accelerite, a Persistent Systems business. It is intended only for the
use of the individual or entity to which it is addressed. If you are not the intended recipient,
you are not authorized to read, retain, copy, print, distribute or use this message. If you
have received this communication in error, please notify the sender and delete all copies
of this message. Accelerite, a Persistent Systems business does not accept any liability for
virus infected mails.

abhinandan.prateek@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message