[jira] [Updated] (MAPREDUCE-4260) Investigate use of JobObject to spawn tasks on Windows

["Bikas Saha (JIRA)" <ji...@apache.org>]

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

Bikas Saha updated MAPREDUCE-4260:
----------------------------------

    Attachment: MAPREDUCE-4260.branch-1-win.patch

Attaching a patch with 
1) bug fixes
2) native code placed in winutils
3) changing TestKillSubProcesses test the new code.

There is a small hack in MiniDFSCluster to make the test run in the debugger by working around Path issues on Windows. Several jira's track the Path issues. 
                
> Investigate use of JobObject to spawn tasks on Windows
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-4260
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4260
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: MAPREDUCE-4260.branch-1-win.patch, MAPREDUCE-4260.patch, test.cpp
>
>
> Currently, the Windows version spawns the task as a normal cmd shell from which other downstream exe's are spawned. However, this is not bullet proof because if an intermediate process exits before its child exits, then the parent child process tree relationship cannot be constructed. Windows has a concept of JobObject that is similar to the setsid behavior used in Linux. The initial spawned task could be launched within its JobObject. Thereafter, process termination, memory management etc could be operated on the JobObject.

--
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