yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

As of late in the Pike cycle, the resource tracker updates its map of
aggregates associated with the resource provider it knows about
everytime it calls `_ensure_resource_provider`. This method is called
quite often, increasingly so as we do more stuff with resource providers
from both the resource tracker and scheduler (both of which use the
report client). This results in a lot of useless work that could create
undue load on both client and server.

There is a long standing TODO to have some kind of cache or timeout so
that we update the aggregate map less often, as updates of those on the
placement server side are relatively infrequent.

We need to balance between doing the updates too often and there being a
gap between when an aggregate change does happen and the map getting
updated.

** Affects: nova
     Importance: Low
     Assignee: Chris Dent (cdent)
         Status: Confirmed


** Tags: placement

** Changed in: nova
     Assignee: (unassigned) => Chris Dent (cdent)

-- 
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/1708252

Title:
  resource tracker updates its map of aggregates too often

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  As of late in the Pike cycle, the resource tracker updates its map of
  aggregates associated with the resource provider it knows about
  everytime it calls `_ensure_resource_provider`. This method is called
  quite often, increasingly so as we do more stuff with resource
  providers from both the resource tracker and scheduler (both of which
  use the report client). This results in a lot of useless work that
  could create undue load on both client and server.

  There is a long standing TODO to have some kind of cache or timeout so
  that we update the aggregate map less often, as updates of those on
  the placement server side are relatively infrequent.

  We need to balance between doing the updates too often and there being
  a gap between when an aggregate change does happen and the map getting
  updated.

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