hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Vasudev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2137) Add support for logaggregation to a path on non-default filecontext
Date Tue, 10 Jun 2014 02:35:02 GMT

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

Varun Vasudev commented on YARN-2137:
-------------------------------------

Sumit, have you tested this with the client? There is a "yarn logs" command that dumps the
logs give an application id. Does the client automatically pick up the right FileContext?

> Add support for logaggregation to a path on non-default filecontext
> -------------------------------------------------------------------
>
>                 Key: YARN-2137
>                 URL: https://issues.apache.org/jira/browse/YARN-2137
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: log-aggregation
>    Affects Versions: 2.4.0
>            Reporter: Sumit Kumar
>         Attachments: YARN-2137.patch
>
>
> Current log-aggregation implementation supports logaggregation to default filecontext
only. This patch is to support logaggregation to any of the supported filesystems within hadoop
eco-system (hdfs, s3, swiftfs etc). So for example a customer could use hdfs as default filesystem
but use s3 or swiftfs for logaggregation. Current implementation makes mixed usages of FileContext+AbstractFileSystem
apis as well as FileSystem apis which is confusing.
> This patch does two things:
> # moves logaggregation implementation to use only FileContext apis
> # adds support for doing log aggregation on non-default filesystem as well.
> # changes TestLogAggregationService to use local filesystem itself instead of mocking
the behavior



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message