hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Kimball (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4420) JobTracker.killJob() doesn't check for the JobID being valid
Date Tue, 04 Nov 2008 21:58:44 GMT

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

Aaron Kimball updated HADOOP-4420:
----------------------------------

    Attachment: hadoop-4420.patch.2

Added null check and log warning on jobid to getJobStatus(); also added null check in o.a.h.m.CompletedJobStore.readJobStatus()
which it calls.


> JobTracker.killJob() doesn't check for the JobID being valid
> ------------------------------------------------------------
>
>                 Key: HADOOP-4420
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4420
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0, 0.20.0
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: hadoop-4420.patch, hadoop-4420.patch.2
>
>
> As with HADOOP-4419, JobTracker.killJob() assumes that the supplied JobID always matches
to a valid job.

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


Mime
View raw message