Scheduler requests unlimited results from placement
Bug #1746294 reported by
Dan Smith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Smith |
Bug Description
The scheduler will request an infinitely-large host set from placement during scheduling operations. This may be very large on big clouds and makes for a huge JSON response from placement to scheduler each time a single host needs to be selected.
Changed in nova: | |
assignee: | nobody → Dan Smith (danms) |
status: | New → In Progress |
tags: | added: scheduler |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: queens-rc-potential |
Changed in nova: | |
assignee: | Dan Smith (danms) → Matt Riedemann (mriedem) |
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Dan Smith (danms) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/531517 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f029784eaf0 d19bd7bb5d4eb66 f1ea37d3036099
Committed: https:/
Submitter: Zuul
Branch: master
commit f029784eaf0d19b d7bb5d4eb66f1ea 37d3036099
Author: Dan Smith <email address hidden>
Date: Fri Jan 5 14:47:50 2018 -0800
Pass limit to /allocation_ requests
This makes us pass an upper limit to placement when doing scheduling
activities. Without this, we'll always receive every host in the
deployment (that has space for the request), which may be very large.
Closes-Bug: #1746294 3d94ccae89d7cac 0426b57b9b6
Change-Id: I1c34964a74123b