Vinod Kumar Vavilapalli commented on YARN-2448:

I believe YARN-2463 was filed in conjunction with this. Linking them so as to 
resolve them together.

Anyways, I too agree we shouldn't pass the entire calculator - it's a server 
artifact - the apps shouldn't really need to figure out which resource is 
dominant etc. May be we need a smaller subset to be a public interface which 
only does the comparison math between resources?

If that is not needed, and as you said, if we just want to return the resource 
types that the scheduler considers as part of its functioning, we may as well 
expose the RM configuration that says which resources are respected.

> RM should expose the name of the ResourceCalculator being used when AMs 
> register
> --------------------------------------------------------------------------------
>                 Key: YARN-2448
>                 URL: https://issues.apache.org/jira/browse/YARN-2448
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>         Attachments: apache-yarn-2448.0.patch, apache-yarn-2448.1.patch
> The RM should expose the name of the ResourceCalculator being used when AMs 
> register, as part of the RegisterApplicationMasterResponse.
> This will allow applications to make better decisions when scheduling. 
> MapReduce for example, only looks at memory when deciding it's scheduling, 
> even though the RM could potentially be using the DominantResourceCalculator.

This message was sent by Atlassian JIRA

Reply via email to