You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/09/11 12:00:47 UTC

[jira] [Created] (YARN-4147) create a yarn.troubleshooting log for logging app launching problems

Steve Loughran created YARN-4147:
------------------------------------

             Summary: create a yarn.troubleshooting log for logging app launching problems
                 Key: YARN-4147
                 URL: https://issues.apache.org/jira/browse/YARN-4147
             Project: Hadoop YARN
          Issue Type: Sub-task
          Components: yarn
    Affects Versions: 2.7.1
            Reporter: Steve Loughran
            Priority: Minor


We can do more in the RM and NMs of logging what's going on with containers —but it gets very noisy in a large cluster.

I propose a {{org.apache.hadoop.yarn.troubleshooting}} log to which the YARN services can log at debug to: by default these would then not get printed. Turn that log to DEBUG and you can get the troubleshooting info —without getting the low-level debug messages from everything else.





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