>>> Nikhil Utane schrieb am 24.10.2016 um 13:22
in
Nachricht
:
> I had set resource utilization to 1. Even then it scheduled 2 resources.
> Doesn't it honor utilization resources if it doesn't find a free node?
Show us the config and the logs, please!
>
> -Nikhil
>
> On Mon, Oct 24, 2016 at 4
>>> Nikhil Utane schrieb am 24.10.2016 um 13:04
in
Nachricht
:
> That is what happened here :(.
> When 2 nodes went down, two resources got scheduled on single node.
> Isn't there any way to stop this from happening. Colocation constraint is
> not helping.
Why don't you try utilization?
>
> -Re
24.10.2016 14:22, Nikhil Utane wrote:
I had set resource utilization to 1. Even then it scheduled 2 resources.
Doesn't it honor utilization resources if it doesn't find a free node?
To make utilization work you need to set both:
* node overall capacity (per-node utilization attribute)
* capacit
I had set resource utilization to 1. Even then it scheduled 2 resources.
Doesn't it honor utilization resources if it doesn't find a free node?
-Nikhil
On Mon, Oct 24, 2016 at 4:43 PM, Vladislav Bogdanov
wrote:
> 24.10.2016 14:04, Nikhil Utane wrote:
>
>> That is what happened here :(.
>> When
24.10.2016 14:04, Nikhil Utane wrote:
That is what happened here :(.
When 2 nodes went down, two resources got scheduled on single node.
Isn't there any way to stop this from happening. Colocation constraint
is not helping.
If it is ok to have some instances not running in such outage cases, yo
That is what happened here :(.
When 2 nodes went down, two resources got scheduled on single node.
Isn't there any way to stop this from happening. Colocation constraint is
not helping.
-Regards
Nikhil
On Sat, Oct 22, 2016 at 12:57 AM, Vladislav Bogdanov
wrote:
> 21.10.2016 19:34, Andrei Borzen
