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

Amareshwari Sriramadasu updated HADOOP-4361:
--------------------------------------------

    Status: Patch Available  (was: Open)

test-patch result:
{noformat}
     [exec]
     [exec] -1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     -1 tests included.  The patch doesn't appear to include any new 
or modified tests.
     [exec]                         Please justify why no tests are needed for 
this patch.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
     [exec]
     [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath 
integrity.
     [exec]
{noformat}

All the core and contrib tests passed on machine except 
TestMiniMRDebugScript(due to HADOOP-4410)

Did not include any unit test because it is difficult to simulate the 
corner-cases. Did the manual testing for the following:
1. Killed job when all slots are full. made sure cleanup is launched and job is 
killed.
2. Killed job during setup.
3. Killed job during cleanup.
4. Kill task action for setup during setup
5. kill task action for cleanup during cleanup


> Corner cases in killJob from command line
> -----------------------------------------
>
>                 Key: HADOOP-4361
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4361
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: patch-4361.txt
>
>
> If the job has occupied all the slots (maps and reduces), and there is kill 
> from command line to kill the job, we have to make sure the cleanup task is 
> eventually launched. Now there is no slot free until one of the attempts 
> completes/failed.
> If there is kill from commandline during job setup, setup task has to be 
> killed, before launching cleanup task.

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

Reply via email to