hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1615) Fix typos in description about delay scheduling
Date Thu, 19 Feb 2015 01:38:11 GMT

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

Hudson commented on YARN-1615:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #7150 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7150/])
YARN-1615. Fix typos in delay scheduler's description. Contributed by Akira Ajisaka. (ozawa:
rev b8a14efdf535d42bcafa58d380bd2c7f4d36f8cb)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java
* hadoop-yarn-project/CHANGES.txt


> Fix typos in description about delay scheduling
> -----------------------------------------------
>
>                 Key: YARN-1615
>                 URL: https://issues.apache.org/jira/browse/YARN-1615
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation, scheduler
>    Affects Versions: 2.6.0
>            Reporter: Akira AJISAKA
>            Assignee: Akira AJISAKA
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 2.7.0
>
>         Attachments: YARN-1615-002.patch, YARN-1615.patch
>
>
> In FSAppAttempt.java there're 4 typos:
> {code}
>    * containers over rack-local or off-switch containers. To acheive this
>    * we first only allow node-local assigments for a given prioirty level,
>    * then relax the locality threshold once we've had a long enough period
>    * without succesfully scheduling. We measure both the number of "missed"
> {code}
> They should be fixed as follows:
> {code}
>    * containers over rack-local or off-switch containers. To achieve this
>    * we first only allow node-local assignments for a given priority level,
>    * then relax the locality threshold once we've had a long enough period
>    * without successfully scheduling. We measure both the number of "missed"
> {code}



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

Mime
View raw message