Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <547033571.1251693812802.JavaMail.jira@brutus>
Date: Sun, 30 Aug 2009 21:43:32 -0700 (PDT)
From: "Sreekanth Ramakrishnan (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-777) A method for finding and tracking
 jobs from the new API
In-Reply-To: <1456065354.1248155954786.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749374#action_12749374 ] 

Sreekanth Ramakrishnan commented on MAPREDUCE-777:
--------------------------------------------------

With respect to
{noformat}
  public class QueueInfo {
    String getName() { return null; }
    String getSchedulingInfo() throws IOException { return null; }
    Job[] getJobs(int maxJobs) throws IOException { return null; }
    QueueState getState() throws IOException { return null; }
  }
{noformat}

Currently the class {{org.apache.hadoop.mapred.JobQueueInfo}} is client only view of the information pertaining to the queue and is not used in framework for any other purpose, why don't we reuse it instead of a creating a new class?

Also, in the framework the concept of queue was nothing but a tag associated with a Job and some schedulers need not honor the queue and can store the job in a single queue rather than in separate queue, are we planning to change that? 

Then, sending a list of jobs for all the client request might not be required as, there are currently two queue commands i.e. {{queue -list}} which prints out list of queues and associated scheduling information and {{queue -info <queuename> [-listjobs]}} the option of list jobs is optional in second case, by using the proposed api we might end up sending list of jobs all the time even tho' client does not request it.

Finally, MAPREDUCE-853 is introducing an hierarchy of queues and we should also try to handle those scenarios in the JIRA. 

> A method for finding and tracking jobs from the new API
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-777
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-777
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: client
>            Reporter: Owen O'Malley
>            Assignee: Amareshwari Sriramadasu
>             Fix For: 0.21.0
>
>         Attachments: m-777.patch, patch-777-1.txt, patch-777-2.txt, patch-777.txt
>
>
> We need to create a replacement interface for the JobClient API in the new interface. In particular, the user needs to be able to query and track jobs that were launched by other processes.

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