Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 8 Aug 2014 14:16:13 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12729518.1406225756884.43400.1407507373000@arcas>
In-Reply-To: <JIRA.12729518.1406225756884@arcas>
References: <JIRA.12729518.1406225756884@arcas>
Subject: [jira] [Commented] (YARN-2352) FairScheduler: Collect metrics on
 duration of critical methods that affect performance
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-2352:
----------------------------------------

Both tests pass locally for me, and the failures seen here are unrelated to the patch. 

Committing this. 

> FairScheduler: Collect metrics on duration of critical methods that affect performance
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-2352
>                 URL: https://issues.apache.org/jira/browse/YARN-2352
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 2.4.1
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: fs-perf-metrics.png, yarn-2352-1.patch, yarn-2352-2.patch, yarn-2352-2.patch, yarn-2352-3.patch, yarn-2352-4.patch, yarn-2352-5.patch, yarn-2352-6.patch
>
>
> We need more metrics for better visibility into FairScheduler performance. At the least, we need to do this for (1) handle node events, (2) update, (3) compute fairshares, (4) preemption.


--
This message was sent by Atlassian JIRA
(v6.2#6252)