hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-483) Improve documentation on log aggregation in yarn-default.xml
Date Wed, 23 Apr 2014 18:01:31 GMT

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

Sandy Ryza commented on YARN-483:

Thanks for the fix [~ajisakaa].  A couple nits:
+    <description>Whether to enable log aggregation. Log aggregation collects
+      each container's log and moves these logs onto a file-system, for e.g.
+      HDFS, after the application completes. Users can access the logs via
+      Application History Server.
+    </description>
each container's log*s*.

I think it would be good to reference the property that determines where these logs go.

I believe the Application History Server is being renamed to the Application Timeline Server.

> Improve documentation on log aggregation in yarn-default.xml
> ------------------------------------------------------------
>                 Key: YARN-483
>                 URL: https://issues.apache.org/jira/browse/YARN-483
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Akira AJISAKA
>         Attachments: YARN-483.patch
> The current documentation for log aggregation is 
> {code}
>   <property>
>     <description>Whether to enable log aggregation</description>
>     <name>yarn.log-aggregation-enable</name>
>     <value>false</value>
>   </property>
> {code}
> This could be improved to explain what enabling log aggregation does.

This message was sent by Atlassian JIRA

View raw message