Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 25744 invoked from network); 13 Aug 2008 11:09:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Aug 2008 11:09:41 -0000 Received: (qmail 31318 invoked by uid 500); 13 Aug 2008 11:09:34 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 31288 invoked by uid 500); 13 Aug 2008 11:09:34 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 31277 invoked by uid 99); 13 Aug 2008 11:09:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 04:09:34 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2008 11:08:46 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6C335234C1B3 for ; Wed, 13 Aug 2008 04:08:44 -0700 (PDT) Message-ID: <1467263674.1218625724442.JavaMail.jira@brutus> Date: Wed, 13 Aug 2008 04:08:44 -0700 (PDT) From: "Hemanth Yamijala (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3930) Decide how to integrate scheduler info into CLI and job tracker web page In-Reply-To: <675325039.1218240644514.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622167#action_12622167 ] Hemanth Yamijala commented on HADOOP-3930: ------------------------------------------ We probably also need a way to get all the configured queues. Something like: - public List getQueues(); By default, this would return the single default queue that is there today in the jobtracker. Makes sense ? > Decide how to integrate scheduler info into CLI and job tracker web page > ------------------------------------------------------------------------ > > Key: HADOOP-3930 > URL: https://issues.apache.org/jira/browse/HADOOP-3930 > Project: Hadoop Core > Issue Type: Improvement > Reporter: Matei Zaharia > Priority: Minor > > We need a way for job schedulers such as HADOOP-3445 and HADOOP-3476 to provide info to display on the JobTracker web interface and in the CLI. The main things needed seem to be: > * A way for schedulers to provide info to show in a column on the web UI and in the CLI - something as simple as a single string, or a map for multiple parameters. > * Some sorting order for jobs - maybe a method to sort a list of jobs. > Let's figure out what the best way to do this is and implement it in the existing schedulers. > My first-order proposal at an API: Augment the TaskScheduler with > * public Map getSchedulingInfo(JobInProgress job) -- returns key-value pairs which are displayed in columns on the web UI or the CLI for the list of jobs. > * public Map getSchedulingInfo(String queue) -- returns key-value pairs which are displayed in columns on the web UI or the CLI for the list of queues. > * public Comparator getJobComparator() -- returns a comparator that can be used to determine the order in which jobs will be run, for sorting the jobs in the CLI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.