[ 
https://issues.apache.org/jira/browse/YARN-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484030#comment-14484030
 ] 

Sidharta Seethana commented on YARN-2901:
-----------------------------------------

IMHO, using calls to LOG.error()/LOG.warn() as proxies for counting 
errors/warnings is flaky at best. It places cumbersome restrictions on code 
requiring that a given error/warning correspond to a single error()/warn() 
call. This is tough to enforce even within a single block of code, let alone 
across multiple functions ( e.g when an exception is thrown/re-thrown and an 
error/warning logged in multiple locations ). I hope this will not lead to a 
restriction on new code in YARN that error/warning should corresponding a 
single error()/warn() call. 

> Add errors and warning metrics page to RM, NM web UI
> ----------------------------------------------------
>
>                 Key: YARN-2901
>                 URL: https://issues.apache.org/jira/browse/YARN-2901
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, resourcemanager
>            Reporter: Varun Vasudev
>            Assignee: Varun Vasudev
>             Fix For: 2.8.0
>
>         Attachments: Exception collapsed.png, Exception expanded.jpg, Screen 
> Shot 2015-03-19 at 7.40.02 PM.png, YARN-2901.addendem.1.patch, 
> apache-yarn-2901.0.patch, apache-yarn-2901.1.patch, apache-yarn-2901.2.patch, 
> apache-yarn-2901.3.patch, apache-yarn-2901.4.patch, apache-yarn-2901.5.patch
>
>
> It would be really useful to have statistics on the number of errors and 
> warnings in the RM and NM web UI. I'm thinking about -
> 1. The number of errors and warnings in the past 5 min/1 hour/12 hours/day
> 2. The top 'n'(20?) most common exceptions in the past 5 min/1 hour/12 
> hours/day
> By errors and warnings I'm referring to the log level.
> I suspect we can probably achieve this by writing a custom appender?(I'm open 
> to suggestions on alternate mechanisms for implementing this).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to