hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest
Date Wed, 01 Jun 2016 21:54:59 GMT

    [ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311202#comment-15311202
] 

Karthik Kambatla commented on YARN-5180:
----------------------------------------

Can we get #2 of my previous comment fixed. And, by constructor, I think I was referring to
the newInstance method. 

Another thought: Given there are only 4 possibilities of ExecutionTypeRequest, should we just
hardcode them to avoid as many objects as container requests? Would this be premature optimization?


> Add ensureExecutionType boolean flag in ResourceRequest
> -------------------------------------------------------
>
>                 Key: YARN-5180
>                 URL: https://issues.apache.org/jira/browse/YARN-5180
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: YARN-5180.001.patch, YARN-5180.002.patch, YARN-5180.003.patch, YARN-5180.004.patch
>
>
> YARN-2882 introduced the concept of *ExecutionTypes*.
> YARN-4335 allowed AMs to specify the ExecutionType in the ResourceRequest.
> This JIRA proposes to add a boolean flag to the ResourceRequest to signal to the Scheduler
that the AM is fine receiving a Container with a different Execution type than what is asked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message