Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0566110364 for ; Tue, 21 Jan 2014 20:05:31 +0000 (UTC) Received: (qmail 13610 invoked by uid 500); 21 Jan 2014 20:05:28 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 13469 invoked by uid 500); 21 Jan 2014 20:05:27 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 13276 invoked by uid 99); 21 Jan 2014 20:05:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Jan 2014 20:05:25 +0000 Date: Tue, 21 Jan 2014 20:05:24 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877801#comment-13877801 ] Karthik Kambatla commented on YARN-1607: ---------------------------------------- Looks mostly good. One more nit: instead of using inconsistent literal values for sleep intervals, can we define a constant SLEEP_INTERVAL and use it through out. Thanks. > TestRM expects the capacity scheduler > ------------------------------------- > > Key: YARN-1607 > URL: https://issues.apache.org/jira/browse/YARN-1607 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Sandy Ryza > Assignee: Sandy Ryza > Attachments: YARN-1607-1.patch, YARN-1607.patch > > > We should either explicitly set the Capacity Scheduler or make it scheduler-agnostic -- This message was sent by Atlassian JIRA (v6.1.5#6160)