[
https://issues.apache.org/jira/browse/YARN-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969088#comment-15969088
]
Jason Lowe commented on YARN-2985:
----------------------------------
Doing a config for branch-2 seems reasonable.
bq. my understanding is that the timeline server is supposed to replace the
JHS, even for deployments that only run MR jobs
This is news to me. The timeline server has no UI, just REST APIs, so there
minimally needs to be something that provides the javascript necessary for the
client browser to render a MapReduce-aware UI. I haven't seen that in trunk,
and without it the MapReduce JHS must still be running if there's going to be a
MapReduce UI for completed jobs.
Even without the timeline server completely replacing the MR JHS, the deletion
service can still be moved in trunk without a config under the following
conditions:
* The timeline server is considered a critical server that always needs to be
running (or we simply document that it must be used when log aggregation is
enabled)
* There's an equivalent way to refresh the config options like can be done with
the deletion service in the MR JHS today.
> YARN should support to delete the aggregated logs for Non-MapReduce
> applications
> --------------------------------------------------------------------------------
>
> Key: YARN-2985
> URL: https://issues.apache.org/jira/browse/YARN-2985
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: log-aggregation, nodemanager
> Affects Versions: 2.8.0
> Reporter: Xu Yang
> Assignee: Steven Rand
> Attachments: YARN-2985-branch-2-001.patch
>
>
> Before Hadoop 2.6, the LogAggregationService is started in NodeManager. But
> the AggregatedLogDeletionService is started in mapreduce`s JobHistoryServer.
> Therefore, the Non-MapReduce application can aggregate their logs to HDFS,
> but can not delete those logs. Need the NodeManager take over the function of
> aggregated log deletion.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
