yahoo-eng-team team mailing list archive

[OpenStack Infra <1524421@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/255405
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3d6fac8dea940b62e88f239c5615acc500b74f05
Submitter: Jenkins
Branch:    master

commit 3d6fac8dea940b62e88f239c5615acc500b74f05
Author: EdLeafe <ed@xxxxxxxxx>
Date:   Wed Dec 9 17:51:52 2015 +0000

    Don't load deleted instances
    
    When the HostManager starts up, it loads the instance information for
    all of the compute nodes. The call it uses, though, includes the records
    for deleted instances, which are not needed, and which can cause
    performance issues for large deployments. This patch adds a filter on
    deleted records.
    
    Closes-bug: 1524421
    
    Change-Id: I404b6baa5504316f447d9c504132183198ff689e


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1524421

Title:
  Host Manager reads deleted instance info on startup

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  In Kilo we added the ability of the HostManager to track information
  about the instances on compute nodes, so that filters that needed this
  information didn't have to constantly make database calls to get it.
  However, the call that is used by HostManager will return deleted
  instance records, which is not useful information and degrades the
  performance. In a large deployment, the overhead of loading the
  records for thousands of deleted instances is causing serious
  performance issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1524421/+subscriptions