yahoo-eng-team team mailing list archive

["Davanum Srinivas \(DIMS\)" <davanum@xxxxxxxxx>]

** Changed in: oslo
       Status: Triaged => Invalid

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

Title:
  Heavily loaded nova-compute instances don't sent reports frequently
  enough

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) essex series:
  Fix Released
Status in Oslo - a Library of Common OpenStack Code:
  Invalid
Status in “nova” package in Ubuntu:
  Fix Released
Status in “nova” source package in Precise:
  Fix Released

Bug description:
  We knows that nova-compute will do report_state to update the service information in DB, And the default report_interval is 5s.
  When scheduler run a new instance, it will check the time that nova-compute updated. If the interval is longer than 60 seconds, Scheduler see the host is dead.

  But when the host(nova-compute) running a lot of instances ( about
  70+) . The report_interval sometimes can be greater then 2minutes.
  This will result in ERROR in scheduler.

  I think report_state should be in a thread, rather than in a eventlet.spawn.
  What about guys think?

  Thanks

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