Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <2095399033.1226660684500.JavaMail.jira@brutus>
Date: Fri, 14 Nov 2008 03:04:44 -0800 (PST)
From: "Sreekanth Ramakrishnan (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4079) Check for invalid queues in capacity
 scheduler
In-Reply-To: <1861612771.1220603864330.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sreekanth Ramakrishnan updated HADOOP-4079:
-------------------------------------------

    Status: Patch Available  (was: Open)

Resubmitting the patch for running thro' Hudson, the patch still applies against the trunk.

> Check for invalid queues in capacity scheduler
> ----------------------------------------------
>
>                 Key: HADOOP-4079
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4079
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 0.19.0
>            Reporter: Hemanth Yamijala
>            Assignee: Sreekanth Ramakrishnan
>             Fix For: 0.20.0
>
>         Attachments: HADOOP-4079-1.patch, HADOOP-4079-2.patch, HADOOP-4079-3.patch
>
>
> The {{ResourceManagerConf}} class that is being moved to the capacity scheduler of HADOOP-3445 needs to check for a queue name that is not configured in the {{resource-manager-conf.xml}} file in its APIs and fail if it is not available. This feature was originally available, but due to subsequent changes in HADOOP-3698, queues are no longer being configured as part of the mentioned configuration file. Hence we need a different mechanism to check for valid queues.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.