Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 19 Feb 2015 02:15:12 +0000 (UTC)
From: "Akira AJISAKA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12689767.1390195908000.82770.1424312112921@Atlassian.JIRA>
In-Reply-To: <JIRA.12689767.1390195908000@Atlassian.JIRA>
References: <JIRA.12689767.1390195908000@Atlassian.JIRA>
 <JIRA.12689767.1390195908797@arcas>
Subject: [jira] [Commented] (YARN-1615) Fix typos in description about delay
 scheduling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Akira AJISAKA commented on YARN-1615:
-------------------------------------

Thanks Tsuyoshi for review and commit.

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