hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6022) Revert changes of AbstractResourceRequest
Date Thu, 22 Dec 2016 19:31:58 GMT

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

Arun Suresh commented on YARN-6022:
-----------------------------------

So, looks like the original class was created to unify Update requests and new Resource Request.
So I think we should capture that in the new class.
Given that the Scheduler deals with resources as requests and returns containers as response,
I was thinking it should have atleast these 3 fields:
# Resource capability
# ContainerId containerToUpdate (defaults to null)
# int numContainers (if containerToUpdate != null, this will be 1)

> Revert changes of AbstractResourceRequest
> -----------------------------------------
>
>                 Key: YARN-6022
>                 URL: https://issues.apache.org/jira/browse/YARN-6022
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Priority: Blocker
>
> YARN-5774 added AbstractResourceRequest to make easier internal scheduler change, this
is not a correct approach: For example, with this change, we need to make AbstractResourceRequest
to be public/stable. And end users can use it like:
> {code}
> AbstractResourceRequest request = ...
> request.setCapability(...)
> {code}
> But AbstractResourceRequest should not be visible by application at all. 
> We need to revert it from branch-2.8 / branch-2 / trunk. 



--
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