[
https://issues.apache.org/jira/browse/CLOUDSTACK-9481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15448719#comment-15448719
]
ASF GitHub Bot commented on CLOUDSTACK-9481:
--------------------------------------------
GitHub user abhinandanprateek opened a pull request:
https://github.com/apache/cloudstack/pull/1667
CLOUDSTACK-9481: Convert MyISAM table to InnoDB for consistency
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shapeblue/cloudstack innodb
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1667.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1667
----
commit 842fb7004c8a7dc2fa8e5a03d8555cdc70febb90
Author: Abhinandan Prateek <[email protected]>
Date: 2016-08-30T10:46:40Z
CLOUDSTACK-9481: Convert MyISAM table to InnoDB for consistency
----
> 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)
