hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-476) ProcfsBasedProcessTree info message confuses users
Date Thu, 18 Apr 2013 22:04:14 GMT

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

Jason Lowe updated YARN-476:
----------------------------

    Fix Version/s: 0.23.8

Thanks, Sandy.  I also committed this to branch-0.23.
                
> ProcfsBasedProcessTree info message confuses users
> --------------------------------------------------
>
>                 Key: YARN-476
>                 URL: https://issues.apache.org/jira/browse/YARN-476
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.0.3-alpha, 0.23.6
>            Reporter: Jason Lowe
>            Assignee: Sandy Ryza
>            Priority: Minor
>             Fix For: 2.0.5-beta, 0.23.8
>
>         Attachments: YARN-476.patch
>
>
> ProcfsBasedProcessTree has a habit of emitting not-so-helpful messages such as the following:
> {noformat}
> 2013-03-13 12:41:51,957 INFO [communication thread] org.apache.hadoop.yarn.util.ProcfsBasedProcessTree:
The process 28747 may have finished in the interim.
> 2013-03-13 12:41:51,958 INFO [communication thread] org.apache.hadoop.yarn.util.ProcfsBasedProcessTree:
The process 28978 may have finished in the interim.
> 2013-03-13 12:41:51,958 INFO [communication thread] org.apache.hadoop.yarn.util.ProcfsBasedProcessTree:
The process 28979 may have finished in the interim.
> {noformat}
> As described in MAPREDUCE-4570, this is something that naturally occurs in the process
of monitoring processes via procfs.  It's uninteresting at best and can confuse users who
think it's a reason their job isn't running as expected when it appears in their logs.
> We should either make this DEBUG or remove it entirely.

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

Mime
View raw message