<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2018-08-02 4:09 GMT+08:00 Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 08/01/2018 02:02 PM, Chris Friesen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 08/01/2018 11:32 AM, melanie witt wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think it's definitely a significant issue that troubleshooting "No allocation<br>
candidates returned" from placement is so difficult. However, it's not<br>
straightforward to log detail in placement when the request for allocation<br>
candidates is essentially "SELECT * FROM nodes WHERE cpu usage < needed and disk<br>
usage < needed and memory usage < needed" and the result is returned from the API.<br>
</blockquote>
<br>
I think the only way to get useful info on a failure would be to break down the huge SQL statement into subclauses and store the results of the intermediate queries.<br>
</blockquote>
<br></span>
This is a good idea and something that can be done.<br></blockquote><div><br></div><div>That sounds like you need separate sql query for each resource to get the <span style="font-size:14px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">intermediate, will that be terrible performance than a single query to get the final result?</span></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Unfortunately, it's refactoring work and as a community, we tend to prioritize fancy features like NUMA topology and CPU pinning over refactoring work.<br>
<br>
Best,<br>
-jay<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>