[ https://issues.apache.org/jira/browse/YARN-2806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220214#comment-14220214 ]
Eric Wohlstadter commented on YARN-2806: ---------------------------------------- Looking at scheduler.AppSchedulingInfo (lines 141-146, trunk): What is the significance of ResourceRequest.ANY, in terms of determining whether to LOG a ResourceRequest? Why only ResourceRequest.ANY? Why is the ANY location the only one which can determine that "updatePendingResources = true"? Are all updated resource requests from the AM initiated with a ResourceRequest at the ANY location? Can all allocate calls from the AM which do not include a ResourceRequest.ANY be considered followup requests to a previous initial request for those resources (e.g. by asking for less number of containers in the followup or by modifying preferred locations in the followup)? {code:title=AppSchedulingInfo(141-146) |borderStyle=solid} if (resourceName.equals(ResourceRequest.ANY)) { if (LOG.isDebugEnabled()) { LOG.debug("update:" + " application=" + applicationId + " request=" + request); } updatePendingResources = true; {code} > 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 > Assignee: Eric Wohlstadter > Attachments: YARN-2806.patch > > > 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)