<div dir="ltr">I think it was a silly mistake. "<span style="color:rgb(0,0,0);font-family:"liberation mono","bitstream vera mono","dejavu mono",monospace;font-size:14px;font-weight:bold;white-space:pre-wrap">placement-strategy</span>" was not enabled.<div>We have enabled it now and testing it out.</div><div><br></div><div>Thanks</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 24, 2016 at 7:35 PM, Ulrich Windl <span dir="ltr"><<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de" target="_blank">Ulrich.Windl@rz.uni-regensburg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>>> Nikhil Utane <<a href="mailto:nikhil.subscribed@gmail.com">nikhil.subscribed@gmail.com</a>> schrieb am 24.10.2016 um 13:22<br>
in<br>
Nachricht<br>
<<a href="mailto:CAGNWmJXMLYnJjsJiPRmrKhcAPb3rNqX9xuWucqmWL5Qa8WwDgw@mail.gmail.com">CAGNWmJXMLYnJjsJiPRmrKhcAPb3r<wbr>NqX9xuWucqmWL5Qa8WwDgw@mail.<wbr>gmail.com</a>>:<br>
<span class="">> I had set resource utilization to 1. Even then it scheduled 2 resources.<br>
> Doesn't it honor utilization resources if it doesn't find a free node?<br>
<br>
</span>Show us the config and the logs, please!<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> -Nikhil<br>
><br>
> On Mon, Oct 24, 2016 at 4:43 PM, Vladislav Bogdanov <<a href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a>><br>
> wrote:<br>
><br>
>> 24.10.2016 14:04, Nikhil Utane wrote:<br>
>><br>
>>> That is what happened here :(.<br>
>>> When 2 nodes went down, two resources got scheduled on single node.<br>
>>> Isn't there any way to stop this from happening. Colocation constraint<br>
>>> is not helping.<br>
>>><br>
>><br>
>> If it is ok to have some instances not running in such outage cases, you<br>
>> can limit them to 1-per-node with utilization attributes (as was suggested<br>
>> earlier). Then, when nodes return, resource instances will return with<br>
(and<br>
>> on!) them.<br>
>><br>
>><br>
>><br>
>>> -Regards<br>
>>> Nikhil<br>
>>><br>
>>> On Sat, Oct 22, 2016 at 12:57 AM, Vladislav Bogdanov<br>
>>> <<a href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a> <mailto:<a href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a>>> wrote:<br>
>>><br>
>>> 21.10.2016 19:34, Andrei Borzenkov wrote:<br>
>>><br>
>>> 14.10.2016 10:39, Vladislav Bogdanov пишет:<br>
>>><br>
>>><br>
>>> use of utilization (balanced strategy) has one caveat:<br>
>>> resources are<br>
>>> not moved just because of utilization of one node is less,<br>
>>> when nodes<br>
>>> have the same allocation score for the resource. So, after<br>
the<br>
>>> simultaneus outage of two nodes in a 5-node cluster, it may<br>
>>> appear<br>
>>> that one node runs two resources and two recovered nodes run<br>
>>> nothing.<br>
>>><br>
>>><br>
>>> I call this a feature. Every resource move potentially means<br>
>>> service<br>
>>> outage, so it should not happen without explicit action.<br>
>>><br>
>>><br>
>>> In a case I describe that moves could be easily prevented by using<br>
>>> stickiness (it increases allocation score on a current node).<br>
>>> The issue is that it is impossible to "re-balance" resources in<br>
>>> time-frames when stickiness is zero (over-night maintenance window).<br>
>>><br>
>>><br>
>>><br>
>>> Original 'utilization' strategy only limits resource<br>
>>> placement, it is<br>
>>> not considered when choosing a node for a resource.<br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
>>> <mailto:<a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a>><br>
>>> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
>>> <<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a>><br>
>>><br>
>>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>>> Getting started:<br>
>>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
>>> <<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a>><br>
>>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a> <mailto:<br>
>>> <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a>><br>
>>> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
>>> <<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a>><br>
>>><br>
>>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>>> Getting started:<br>
>>> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
>>> <<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a>><br>
>>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
>>> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
>>><br>
>>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
>>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>>><br>
>>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
>> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
>><br>
>> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
>> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</div></div></blockquote></div><br></div>