Wangda Tan commented on YARN-2555:

I think they're different, proposal of YARN-2422 is making a flexible 
max-allocation. And this JIRA focus on reject ResourceRequest when its larger 
than biggest node in the cluster.

IMHO, we don't need to both of them, it is very possible nodes connect to RM 
after application submitted, especially in virtual cluster environment.
And as [~sandyr] commented, it's weird to have NM variable affect RM 
configuration. Having a fixed max-allocation is useful to make sure user 
doesn't get more resource than he needed.

> Effective max-allocation-* should consider biggest node
> -------------------------------------------------------
>                 Key: YARN-2555
>                 URL: https://issues.apache.org/jira/browse/YARN-2555
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.5.1
>            Reporter: Karthik Kambatla
>            Assignee: Wei Yan
> The effective max-allocation-mb should be 
> min(admin-configured-max-allocation-mb, max-mb-on-one-node), so we can reject 
> container requests for resources larger than any node. Today, these requests 
> wait forever. 
> We should do this for all resources and update the effective value on node 
> updates. 

This message was sent by Atlassian JIRA

Reply via email to