[
https://issues.apache.org/jira/browse/YARN-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703107#comment-15703107
]
Botong Huang edited comment on YARN-5525 at 11/28/16 9:04 PM:
--------------------------------------------------------------
Thanks [~xgong], yes this is an issue. I am thinking if the customer needs to
customize the location of the logs, and choose not to upload the logs into the
configured RemoteRootDir assumed by Yarn, then I assume they will handle the
downstream log usage, and it is okay for yarn log cli and RM UI not to be able
to find it?
Or in their private implementation, they can copy the logs to both places. One
for Yarn to understand, and one for their customized use.
was (Author: botong):
Thanks [~xgong], yes this is an issue. I am thinking if the customer needs to
customize the location of the logs, and choose not to upload the logs into the
configured RemoteRootDir assumed by Yarn, then I assume they will handle the
downstream log usage, and it is okay for yarn log cli and RM UI not to be able
to find it?
> Make log aggregation service class configurable
> -----------------------------------------------
>
> Key: YARN-5525
> URL: https://issues.apache.org/jira/browse/YARN-5525
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: log-aggregation
> Reporter: Giovanni Matteo Fumarola
> Assignee: Botong Huang
> Priority: Minor
> Labels: oct16-medium
> Attachments: YARN-5525.v1.patch, YARN-5525.v2.patch,
> YARN-5525.v3.patch, YARN-5525.v4.patch, YARN-5525.v5.patch
>
>
> Make the log aggregation class configurable and extensible, so that
> alternative log aggregation behaviors like app specific log aggregation
> directory, log aggregation format can be implemented and plugged in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
