Wangda Tan commented on YARN-4335:

Thanks [~kkaranasos] for updating the patch

bq. Just double-checking: do you mean adding an additional description in the 
javadoc of the ExecutionType?

87        @Public
88        @Stable
89        public static ResourceRequest newInstance(Priority priority, String 
hostName, ...
Should be unstable as well.

As [~kasha] 
 on YARN-1011:
bq. Given this complication, I would prefer we do not involve AMs in the 
decision-making process. Based on the need and usecases, we could revisit this 
at a later time. Note that YARN-4335 adds this to ResourceRequest for 
distributed scheduling, and even there they are not entirely sure if it needs 
to be a part.

I'm not sure if there's any tasks of YARN-2877 directly depends on it, It's 
fine to me to commit this to YARN-2877 branch, but I prefer to hold commit 
unless any tasks require it.

> Allow ResourceRequests to specify ExecutionType of a request ask
> ----------------------------------------------------------------
>                 Key: YARN-4335
>                 URL: https://issues.apache.org/jira/browse/YARN-4335
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-4335-yarn-2877.001.patch, YARN-4335.002.patch
> YARN-2882 introduced container types that are internal (not user-facing) and 
> are used by the ContainerManager during execution at the NM.
> With this JIRA we are introducing (user-facing) resource request types that 
> are used by the AM to specify the type of the ResourceRequest.
> We will initially support two resource request types: CONSERVATIVE and 
> CONSERVATIVE resource requests will be handed internally to containers of 
> GUARANTEED type, whereas OPTIMISTIC resource requests will be handed to 
> QUEUEABLE containers.

This message was sent by Atlassian JIRA

Reply via email to