share service takes too long to complete startup in large-scale environment

Bug #1909847 reported by haixin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Medium
haixin

Bug Description

   when we need to start or restart manila share service, will call init_host().
and call ensure_driver_resources() in init_host(),
will call self.driver.ensure_shares or self.driver.ensure_share to update all share instances in that host. Currently, only NetApp and LVM implement self.driver.ensure_shares, Other manufacturers are using self.driver.ensure_share.
   in large-scale environment, there are lot of share instances in one host. this will lead to take much time to ensure_share.
   so we can put this operation into the thread pool to speed up the startup of the service.

Revision history for this message
Tom Barron (tpb) wrote :
tags: added: drivers performance
Changed in manila:
status: New → Confirmed
Vida Haririan (vhariria)
Changed in manila:
importance: Undecided → Medium
assignee: nobody → haixin (haixin77)
Revision history for this message
Vida Haririan (vhariria) wrote :
Changed in manila:
milestone: none → wallaby-2
Changed in manila:
milestone: wallaby-2 → wallaby-3
status: Confirmed → In Progress
tags: added: wallaby-rc-bugsquash
Changed in manila:
milestone: wallaby-3 → wallaby-rc1
Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 12.0.0.0rc1

This issue was fixed in the openstack/manila 12.0.0.0rc1 release candidate.

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.