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-6593) [API] Introduce Placement Constraint object
Date Tue, 01 Aug 2017 22:39:00 GMT

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

Arun Suresh commented on YARN-6593:

bq. Actually, my comments should apply to YARN-6594 rather this jira.
[~jianhe], I am guessing you are referring to the *AllocationTags* .. then yes, we should
continue that discussion in YARN-6594, since this pertains just to the *PlacementConstraint*
object. (Can you please cross-post it there as well ?)  

My opinion though is that the allocation tags should remain a list of string keys. I understand
this might offload some work from the AM, but do you see it helping the RM/scheduler in making
a scheduling decision ? If it is just to select a bunch of containers, one can still perform
a search like: select containers where allocationtags contains "env=test" etc. Forcing the
tags to be a map might even make the querying more complicated.

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

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

View raw message