[
https://issues.apache.org/jira/browse/MAPREDUCE-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291193#comment-13291193
]
Bikas Saha commented on MAPREDUCE-4260:
---------------------------------------
1. I agree the check looks a bit weird. But I put that in because I am not sure
how this will affect existing Cygwin installations where people may not have
winutils built. I think that is something we need to figure out. The code in
winutils already has the dependency comment.
2. Will do
3. Again, I am mainly concerned about installations that dont have winutils and
also to guard against any unexpected use cases that might break. I agree that
this code should disappear soon.
4. Will do
5. From what I understand this error would come if the
JOBOBJECT_BASIC_PROCESS_ID_LIST does not have enough space to return
information about all processes. In that case, one needs to reallocate the
structure based on the value of NumberOfAssignedProcesses and call
QueryInformationJobObject() again. Since I am not interested in per process
information I choose to ignore that error. Let me know if my understanding is
not accurate.
> 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
