OpenStack Shared File Systems Service (Manila)

share_instances table misses index on share_id

Bug #1776495 reported by Maurice Escher on 2018-06-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	OpenStack Shared File Systems Service (Manila)	Fix Released	Undecided	Maurice Escher

Hi,

with several thousand shares our database performance is getting worse.

I analyzed the expensive statements and came to the conclusion to add an index on share_id to the share_instances table.

This is bug 1 of 3 of this kind, there will come two more indices.

Cheers,
Maurice

OpenStack Infra (hudson-openstack) on 2018-06-12

Changed in manila:
assignee:	nobody → Maurice Schreiber (maurice-schreiber)
status:	New → In Progress

Revision history for this message

Maurice Escher (maurice-escher) wrote on 2018-06-20:

This was tried to fix in https://bugs.launchpad.net/manila/+bug/1666547 before for all tables

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-07-20: Fix merged to manila (master)

commit c6bc537fb274999e57815e2b00c4327d15799381
Author: Maurice Schreiber <email address hidden>
Date: Tue Jun 12 12:50:19 2018 +0200

Add share instance index on share_id

The index on the foreign key is created on InnoDB mysql implicitly.
This makes it explicit.

Closes-Bug: #1776495
Change-Id: I6ff5cee86997d0d756b4852fa4d0e7bcfcc9c1cf

Changed in manila:
status:	In Progress → Fix Released

Revision history for this message

This issue was fixed in the openstack/manila 7.0.0.0b3 development milestone.

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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