hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreekanth Ramakrishnan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5020) JobStatus of killed JobInProgress does carry forward start time of the Job
Date Wed, 14 Jan 2009 11:02:59 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663723#action_12663723

Sreekanth Ramakrishnan commented on HADOOP-5020:

In JobInitializationPoller, we do a check for the jobs which have been killed/scheduled at
start of every polling in-order to clean up the jobs from the job queue. The way the job is
removed from the TreeMap is by doing following:
jobList.remove(new JobSchedulingInfo(jobInProgress));

The JobSchedulingInfo requires job status which is present in the JobInProgress while construction
of the object. When we do a remove from tree map, since the scheduling information differ
because of zero stat time, it fails.

The scheduler core does not rely on this way of job removal as it listens to job status changed
events in which old and new job status are passed so that takes care of removal from running
jobs queue which scheduler maintains.

> JobStatus of killed JobInProgress does carry forward start time of the Job
> --------------------------------------------------------------------------
>                 Key: HADOOP-5020
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5020
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Sreekanth Ramakrishnan
> If an initialized job is killed, the jobs start time is set to zero.

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

View raw message