hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-450) Define value for * in the scheduling protocol
Date Thu, 07 Mar 2013 19:24:13 GMT

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

Zhijie Shen commented on YARN-450:

Yes, the string shouldn't be a configurable item, which seems not to be suitable to be placed
in YarnConfiguration.

On the other side, I'm wondering whether it good to have a project-wide constant aggregation
class, i.e., YarnConstants (like the existing HdfsConstants and ApplicationConstants). The
constant string mentioned here and the exit codes mentioned in YARN-444 can be placed in it.
> Define value for * in the scheduling protocol
> ---------------------------------------------
>                 Key: YARN-450
>                 URL: https://issues.apache.org/jira/browse/YARN-450
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Bikas Saha
>            Assignee: Zhijie Shen
>         Attachments: YARN-450_1.patch, YARN-450_2.patch
> The ResourceRequest has a string field to specify node/rack locations. For the cross-rack/cluster-wide
location (ie when there is no locality constraint) the "*" string is used everywhere. However,
its not defined anywhere and each piece of code either defines a local constant or uses the
string literal. Defining "*" in the protocol and removing other local references from the
code base will be good.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message