hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-6593) [API] Introduce Placement Constraint object
Date Tue, 01 Aug 2017 22:06:02 GMT

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

Jian He edited comment on YARN-6593 at 8/1/17 10:05 PM:
--------------------------------------------------------

Actually, my comments should apply to YARN-6594  rather this jira.  

For example, I want to associate some meta info like "env=test" and "version=v2" info to the
container and the AM can define the keys by itself. AM can then do select based on these key
and values for the containers returned.
To me, the tag is not just used for scheduling decisions. It's also for associating metainfo
to the container, otherwise, the AM has to maintain and persist the mapping by itself. If
YARN natively supports this, it'll be a lot easier for the AM.  

bq. I have some first examples in PlacementConstraints. Do you think we should add them in
a different class?
I was thinking having a class which lists all sorts scenarios and the implementation, user
can pretty much copy the code as needed.  Reading javadoc is one option but still not straightfoward.
Or if the javadoc is comprehensive to cover all scenarios in one place, rather than letting
user look for different places, that should also be fine. 


was (Author: jianhe):
Actually, my comments should apply to YARN-6594  rather this jira.  

For example, I want to associate some meta info like "env=test" and "version=v2" info to the
container and the AM can define the keys by itself. AM can then do select based on these key
and values for the containers returned.
To me, the tag is not just used for scheduling decisions. It's also for associating metainfo
to the container, otherwise, the AM has to maintain and persist the mapping by itself. If
YARN natively supports this, it'll be a lot easier for the AM.  

bq. I have some first examples in PlacementConstraints. Do you think we should add them in
a different class?
I was thinking having a class which lists all sorts scenarios and the API definitions, user
can pretty much copy the semantics.  Reading javadoc is one option but still not straightfoward.


> [API] Introduce Placement Constraint object
> -------------------------------------------
>
>                 Key: YARN-6593
>                 URL: https://issues.apache.org/jira/browse/YARN-6593
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Konstantinos Karanasos
>            Assignee: Konstantinos Karanasos
>         Attachments: YARN-6593.001.patch, YARN-6593.002.patch, YARN-6593.003.patch, YARN-6593.004.patch,
YARN-6593.005.patch, YARN-6593.006.patch, YARN-6593.007.patch, YARN-6593.008.patch
>
>
> Just removed Fixed version and moved it to target version as we set fix version only
after patch is committed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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