[ https://issues.apache.org/jira/browse/YARN-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751924#comment-13751924 ]
Vinod Kumar Vavilapalli commented on YARN-1109: ----------------------------------------------- Yeah, I've been trying to fix this too. Two things - The containerId can be compact. - Unless a containers state changes, we don't need to print the log message. Setting newbie tag. > Consider throttling or demoting NodeManager "Sending out status for > container" logs > ----------------------------------------------------------------------------------- > > Key: YARN-1109 > URL: https://issues.apache.org/jira/browse/YARN-1109 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Affects Versions: 2.1.0-beta > Reporter: Sandy Ryza > Labels: newbie > > Diagnosing NodeManager and container launch problems is made more difficult > by the enormous number of logs like > {code} > Sending out status for container: container_id {, app_attempt_id {, > application_id {, id: 18, cluster_timestamp: 1377559361179, }, attemptId: 1, > }, id: 1337, }, state: C_RUNNING, diagnostics: "Container killed by the > ApplicationMaster.\n", exit_status: -1000 > {code} > On an NM with a few containers I am seeing tens of these per second. -- 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