Disable BuildFailureWeigher

Disable the BuildFailureWeigher used when weighting hosts during
instance scheduling. A single build failure will result in a
-1000000 weighting which effectively excludes the hypervisor
from the scheduling decision.

A bad image can result in build failures resulting in a heavy
load on hypervisors which have not had a build failure with
those that have effectively being ignored; the build failure
count will be reset on a successful build but due to the high
weighting this won't happen until all resources on known good
hypervisors have been completely consumed.

Change-Id: I4d4367ef20e2a20aee1e26d4a0ec69cad2ac69d6
Closes-Bug: 1818239
This commit is contained in:
James Page 2019-03-04 09:25:46 +00:00
parent fe0ba3b883
commit c5029e9831
2 changed files with 14 additions and 0 deletions

View File

@ -185,6 +185,13 @@ enabled_filters = {{ scheduler_default_filters }},{{ additional_neutron_filters
enabled_filters = {{ scheduler_default_filters }}
{% endif %}
# Disable BuildFailureWeigher as any failed build will result
# in a very low weighting for the hypervisor, resulting in
# instances all being scheduled to hypervisors with no build
# failures.
# https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239
build_failure_weight_multiplier = 0.0
[api]
auth_strategy=keystone
{% if vendor_data or vendor_data_url -%}

View File

@ -191,6 +191,13 @@ enabled_filters = {{ scheduler_default_filters }},{{ additional_neutron_filters
enabled_filters = {{ scheduler_default_filters }}
{% endif %}
# Disable BuildFailureWeigher as any failed build will result
# in a very low weighting for the hypervisor, resulting in
# instances all being scheduled to hypervisors with no build
# failures.
# https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239
build_failure_weight_multiplier = 0.0
[api]
auth_strategy=keystone
{% if vendor_data or vendor_data_url -%}