[
https://issues.apache.org/jira/browse/MAPREDUCE-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579442#comment-13579442
]
Karthik Kambatla commented on MAPREDUCE-5005:
---------------------------------------------
A combination of the two approaches might be the best. Essentially, do what
Sandy says, and then if the process hasn't died, check the status of the
process in /proc/pid.
Will put up a preliminary patch, and we can reiterate if need be.
> TestProcfsProcessTree#testProcessTree() doesn't wait long enough for the
> process to die
> ---------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5005
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5005
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.0.2-alpha
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
>
> TestProcfsProcessTree#testProcessTree fails occasionally with the following
> stack trace
> {noformat}
> Stack Trace:
> junit.framework.AssertionFailedError: expected:<false> but was:<true>
> at
> org.apache.hadoop.util.TestProcfsBasedProcessTree.testProcessTree(TestProcfsBasedProcessTree.java)
> {noformat}
> kill -9 is executed asynchronously, the signal is delivered when the process
> comes out of the kernel (sys call). Checking if the process died immediately
> after can fail at times.
--
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
