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

Hadoop QA commented on YARN-1109:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12610521/YARN-1109.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2297//console

This message is automatically generated.

> 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
>            Assignee: haosdent
>              Labels: newbie
>         Attachments: YARN-1109.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to