[
https://issues.apache.org/jira/browse/HADOOP-8733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456271#comment-13456271
]
Bikas Saha commented on HADOOP-8733:
------------------------------------
Actually, the TT is informed of the spawned process identifier by the child
process (via TaskUmbilicalProtocol.getTask()). On Linux, this is the Linux OS
pid set via the shell script. On Windows it is the job object identifier set by
the TT (currently set to task attempt id). The child obtains the value from ENV
variable.
The MXBean code is a fallback to get the process OS pid in case the ENV var is
not set. This works cross platform on most JDK's. This is relevant in Windows
only when we dont use job objects for spawning processes (ie directly spawning
Windows processes).
> TestStreamingTaskLog, TestJvmManager, TestLinuxTaskControllerLaunchArgs fail
> on Windows
> ---------------------------------------------------------------------------------------
>
> Key: HADOOP-8733
> URL: https://issues.apache.org/jira/browse/HADOOP-8733
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 1-win
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: HADOOP-8733-scripts.2.patch,
> HADOOP-8733-scripts.2.patch, HADOOP-8733-scripts.patch
>
>
> Jira tracking test failures related to test .sh script dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
