← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1550098] [NEW] Disk resource consumption is inconsistent between scheduler and resource tracker

 

Public bug reported:

The way scheduler consumes disk resources in host state is inconsistent
with RT's way in compute service.

The scheduler consumes "free_disk_mb" in its host state.
https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L266

It comes from the min value of "free_disk_gb" and "disk_available_least" in ComputeNode object.
https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L189-L201

But compute node changes "local_gb_used" instead in consuming resources
from a request.
https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L709-L710


There is a inconsistent gap(confirmed) of compute node state between
scheduler and resource tracker, but somehow the compute node will be
updated by virt driver to the consistent status after maybe 10 seconds.

** Affects: nova
     Importance: Undecided
     Assignee: Yingxin (cyx1231st)
         Status: In Progress

** Changed in: nova
     Assignee: (unassigned) => Yingxin (cyx1231st)

** Changed in: nova
       Status: New => In Progress

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

Title:
  Disk resource consumption is inconsistent between scheduler and
  resource tracker

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The way scheduler consumes disk resources in host state is
  inconsistent with RT's way in compute service.

  The scheduler consumes "free_disk_mb" in its host state.
  https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L266

  It comes from the min value of "free_disk_gb" and "disk_available_least" in ComputeNode object.
  https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L189-L201

  But compute node changes "local_gb_used" instead in consuming
  resources from a request.
  https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L709-L710


  There is a inconsistent gap(confirmed) of compute node state between
  scheduler and resource tracker, but somehow the compute node will be
  updated by virt driver to the consistent status after maybe 10
  seconds.

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


Follow ups