18 nova mysql database tables are not explicitly Innodb

Bug #972831 reported by Sean Dague
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Sean Dague

Bug Description

The following database tables are set to the database engine default when created (the default on many mysql installations is MyISAM), which may have performance implications due to only table level locking on MyISAM.

 agent_builds
 aggregate_hosts
 aggregate_metadata
 aggregates
 block_device_mapping
 bw_usage_cache
 dns_domains
 instance_faults
 instance_type_extra_specs
 provider_fw_rules
 s3_images
 sm_backend_config
 sm_flavors
 sm_volume
 virtual_storage_arrays
 volume_metadata
 volume_type_extra_specs
 volume_types

This could be solved with a migration that forces those tables to Innodb

Tags: db
Changed in nova:
assignee: nobody → Sean Dague (sdague-b)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/6811
Committed: http://github.com/openstack/nova/commit/ff19fd40ea90da1b47bdaa26522f0a30ca18e73f
Submitter: Jenkins
Branch: master

commit ff19fd40ea90da1b47bdaa26522f0a30ca18e73f
Author: Sean Dague <email address hidden>
Date: Mon Apr 9 15:19:11 2012 -0400

    make all mysql tables explicitly innodb

    Fixes bug #972831

    Change-Id: I5692ea3a5c03e65ac8392ba9697dbb4dca285f9c

Changed in nova:
status: In Progress → Fix Committed
aeva black (tenbrae)
tags: added: db
Devin Carlen (devcamcar)
Changed in nova:
importance: Undecided → Medium
milestone: none → folsom-1
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: folsom-1 → 2012.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.