[
https://issues.apache.org/jira/browse/CLOUDSTACK-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448727#comment-15448727
]
ASF GitHub Bot commented on CLOUDSTACK-9481:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1667
@abhinandanprateek can you reopen this for 4.9 branch, since it's a bugfix.
LTS users should all be on innodb to avoid any replication issues, please also
move the changes suitably to 4.9.0->4.9.1(.0) upgrade path sql. Otherwise LGTM.
Tried on a local setup. To list tables that are on non-InnoDb engines:
`SELECT table_schema,table_name,engine FROM information_schema.tables WHERE
engine != 'InnoDB' AND table_schema NOT IN
('mysql','performance_schema','information_schema');`
Except for following tables, all should be on InnoDb engine.
table_schema | table_name | engine
--- | --- | ---
cloud | op_lock | MEMORY
cloud | op_nwgrp_work | MEMORY
> Convert MyISAM table to InnoDB for consistency
> ----------------------------------------------
>
> Key: CLOUDSTACK-9481
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9481
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.9.0
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
> Fix For: 4.9.1
>
>
> These following tables in cloud schema
> load_balancer_cert_map
> monitoring_services
> nic_ip_alias
> sslcerts
> and following in cloud_usage schema
> quota_account
> use MyISAM. There is not reason that these few tables use MyISAM and these
> should be altered to use Innodb
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
