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

Posted to yarn-dev@hadoop.apache.org by "Xuan Gong (JIRA)" <ji...@apache.org> on 2015/05/07 18:54:00 UTC

[jira] [Resolved] (YARN-2137) Add support for logaggregation to a path on non-default filecontext

     [ https://issues.apache.org/jira/browse/YARN-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xuan Gong resolved YARN-2137.
-----------------------------
    Resolution: Duplicate

> 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
>            Assignee: 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.3.4#6332)