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

Allen Wittenauer commented on YARN-2806:
----------------------------------------

I saw all the debug code sitting in cap sched, but that's sort of the wrong 
layer as well.

We're basically trying to get a sense of how long container requests are 
hanging around for a given AM.  Today, we appear to log on either the failure 
or the success of the request.  But we don't log when the request was actually 
made.  I was thinking about pushing this into the audit log might be the way to 
go since it already logs the rest of the job life cycle.

> log container allocation requests
> ---------------------------------
>
>                 Key: YARN-2806
>                 URL: https://issues.apache.org/jira/browse/YARN-2806
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>
> I might have missed it, but I don't see where we log application container 
> requests outside of the DEBUG context.  Without this being logged, we have no 
> idea on a per application the lag an application might be having in the 
> allocation system. 
> We should probably add this as an event to the RM audit log.



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

Reply via email to