Issue Details (XML | Word | Printable)

Key: HADOOP-4420
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Aaron Kimball
Reporter: Steve Loughran
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Hadoop Common

JobTracker.killJob() doesn't check for the JobID being valid

Created: 15/Oct/08 01:15 PM   Updated: 08/Jul/09 04:53 PM
Return to search
Component/s: None
Affects Version/s: 0.18.0, 0.18.1, 0.18.2
Fix Version/s: 0.19.1

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works hadoop-4420.patch 2008-10-30 07:31 AM Aaron Kimball 2 kB
File Licensed for inclusion in ASF works hadoop-4420.patch.2 2008-11-04 09:57 PM Aaron Kimball 3 kB
Issue Links:
Incorporates
 

Hadoop Flags: Reviewed
Resolution Date: 03/Dec/08 03:09 PM


 Description  « Hide
As with HADOOP-4419, JobTracker.killJob() assumes that the supplied JobID always matches to a valid job.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Aaron Kimball added a comment - 30/Oct/08 07:32 AM
This also fixes HADOOP-4419 at the same time

Aaron Kimball added a comment - 30/Oct/08 10:30 AM
Should also add: no unit tests, because it's just straightforward null checks.

Vinod K V added a comment - 30/Oct/08 10:32 AM
For Hadoop-0.20, we should think about ways of informing clients about the failures, instead of just returning silently, as Hemanth pointed out here. This needs API changes and so the approach in the current patch is fine for 0.19.

Some comments about this patch.

  • You don't have a null check for JobID in setJobPriority.
  • The update you made for Changes.txt is not getting applied cleanly. I think you can leave that to be done by the committer of this patch.

Hadoop QA added a comment - 30/Oct/08 01:15 PM
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393039/hadoop-4420.patch
against trunk revision 709040.

+1 @author. The patch does not contain any @author tags.

-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 findbugs. The patch does not introduce any new Findbugs warnings.

+1 Eclipse classpath. The patch retains Eclipse classpath integrity.

+1 core tests. The patch passed core unit tests.

+1 contrib tests. The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3511/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3511/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3511/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3511/console

This message is automatically generated.


Aaron Kimball added a comment - 04/Nov/08 09:57 PM
Added null check and log warning on jobid to getJobStatus(); also added null check in o.a.h.m.CompletedJobStore.readJobStatus() which it calls.

Hadoop QA added a comment - 27/Nov/08 01:58 AM
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12393334/hadoop-4420.patch.2
against trunk revision 720930.

+1 @author. The patch does not contain any @author tags.

-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.

+1 javadoc. The javadoc tool did not generate any warning messages.

+1 javac. The applied patch does not increase the total number of javac compiler warnings.

+1 findbugs. The patch does not introduce any new Findbugs warnings.

+1 Eclipse classpath. The patch retains Eclipse classpath integrity.

-1 core tests. The patch failed core unit tests.

+1 contrib tests. The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3656/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3656/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3656/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3656/console

This message is automatically generated.


Aaron Kimball added a comment - 27/Nov/08 03:04 AM
core test failure is due to something in DFS testFileAppend – Can't see how it's related to this.

Tom White added a comment - 03/Dec/08 03:09 PM
I've just committed this. Thanks Aaron!

See HADOOP-4725 for a follow-on feature to notify clients when they pass bad job IDs.


Hudson added a comment - 06/Dec/08 02:02 PM