[
https://issues.apache.org/jira/browse/YARN-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15703613#comment-15703613
]
Xuan Gong commented on YARN-5525:
---------------------------------
bq. 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?
I do not think that we should assume the customer can handle everything.
In my opinion, we should handle how to aggregate the logs and how to fetch the
logs at the same time. If we open a window for the customer which allows them
to customize the log aggregation service, we/they have to provide a way to
fetch the logs as well.
> 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]
