[
https://issues.apache.org/jira/browse/YARN-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846351#comment-16846351
]
tianjuan edited comment on YARN-9576 at 5/23/19 2:15 AM:
---------------------------------------------------------
Wangda, thanks for your reply. But previously, with node heartbeat(or aysnc
scheduler), in this case, reservation can happen on several nodes, and finally
trigger preemption from queueA, but with ResourceUsageMultiNodeLookupPolicy,
since the order policy will always be h1,h2,..h9,h10, and there will always be
one container re-reverved on node h1, no other reservation happen on other
nodes, preemption will neven happen.
was (Author: jutia):
Wangda, thanks for your reply. But previously, with node heartbeat(or aysnc
scheduler), in this case, reservation can happen on several nodes, and finally
trigger preemption from queueA, but with ResourceUsageMultiNodeLookupPolicy,
the order policy will always be h1,h2,..h9,h10, and there will always be one
container re-reverved on node h1, no other reservation happen on other nodes,
preemption will neven happen.
> ResourceUsageMultiNodeLookupPolicy may cause Application starve forever
> ------------------------------------------------------------------------
>
> Key: YARN-9576
> URL: https://issues.apache.org/jira/browse/YARN-9576
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: tianjuan
> Priority: Major
>
> seems that ResourceUsageMultiNodeLookupPolicy in YARN-7494 may cause
> Application starve forever
> for example, there are 10 nodes(h1,h2,...h9,h10), each has 8G memory in
> cluster, and two queues A,B, each is configured with 50% capacity.
> firstly there are 10 jobs (each requests 6G respurce) is submited to queue A,
> and each node of the 10 nodes will have a contianer allocated.
> Afterwards, another job JobB which requests 3G resource is submited to queue
> B, and there will be one container with 3G size reserved on node h1,
> with ResourceUsageMultiNodeLookupPolicy, the order policy will always be
> h1,h2,..h9,h10, and there will always be one container re-reverved on node
> h1, no other reservation happen, JobB will hang forever.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
