[
https://issues.apache.org/jira/browse/MAPREDUCE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438912#comment-13438912
]
Hudson commented on MAPREDUCE-4570:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2677 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2677/])
MAPREDUCE-4570. ProcfsBasedProcessTree#constructProcessInfo() prints a
warning if procfsDir/<pid>/stat is not found. (Ahmed Radwan via bobby)
(Revision 1375687)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1375687
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/util/ProcfsBasedProcessTree.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/ProcfsBasedProcessTree.java
> ProcfsBasedProcessTree#constructProcessInfo() prints a warning if
> procfsDir/<pid>/stat is not found.
> ----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4570
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4570
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Reporter: Ahmed Radwan
> Assignee: Ahmed Radwan
> Priority: Minor
> Fix For: 0.23.3, 2.1.0-alpha, 3.0.0, 2.2.0-alpha
>
> Attachments: MAPREDUCE-4570.patch
>
>
> I think a warning is misleading in this case. What is happening here is that
> the list of all processes in the system is found, and then later the
> procfsDir/<pid>/stat file for each is opened. This warning is thrown when the
> process finishes before the stat file is opened, and hence the file is no
> longer there. This could normally happen, and shouldn't signify a waring. An
> info message is sufficient. I'll be uploading a patch momentarily.
--
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
