You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/03/25 08:29:25 UTC

[jira] [Commented] (HADOOP-11138) Stream yarn daemon and container logs through log4j

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

Hadoop QA commented on HADOOP-11138:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} | {color:red} HADOOP-11138 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12671993/HADOOP-11138-trunk.patch |
| JIRA Issue | HADOOP-11138 |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/8924/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> Stream yarn daemon and container logs through log4j
> ---------------------------------------------------
>
>                 Key: HADOOP-11138
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11138
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 2.6.0
>            Reporter: shreyas subramanya
>            Assignee: Ying Zhang
>            Priority: Minor
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-11138-1.patch, HADOOP-11138-trunk.patch, HADOOP-11138.patch
>
>
> Resource manager, node manager, history server, application master and other container syslogs can be streamed by configuring a log4j SocketAppender in the root loggers.



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