Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Wed, 27 Jun 2012 22:48:44 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <629781497.64317.1340837324319.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1729371037.31973.1340146482766.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (MAPREDUCE-4355) Add RunningJob.getJobStatus()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla updated MAPREDUCE-4355:
----------------------------------------

    Attachment: MR-4355_mr1.patch

Updated patch for MR1.

ensureFreshStatus() calls updateStatus() only after a particular amount of time has passed since previous updateStatus().

For getJobStatus(), to get the latest status, we need to call updateStatus(). Do you suggest calling ensureFreshStatus() instead for consistency?
                
> Add RunningJob.getJobStatus()
> -----------------------------
>
>                 Key: MAPREDUCE-4355
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4355
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv1, mrv2
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>             Fix For: 1.1.0, 2.0.1-alpha
>
>         Attachments: MR-4355_mr1.patch, MR-4355_mr1.patch, MR-4355_mr2.patch
>
>
> Usecase: Read the start/end-time of a particular job.
> Currently, one has to iterate through JobClient.getAllJobStatuses() and iterate through them. JobClient.getJob(JobID) returns RunningJob, which doesn't hold the job's start time.
> Adding RunningJob.getJobStatus() solves the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira