[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995432#comment-14995432
]
Naganarasimha G R commented on YARN-4183:
-----------------------------------------
Hi [~jeagles] ,[~mitdesai] & [~xgong],
Sorry to pitch in very late on this, but IMHO i would like differ from
the approach taken in the patch for :
* The purpose of using
"yarn.timeline-service.generic-application-history.enabled" was kept for only
kept only to determine whether clients needs to pick the information from
history server or only RM. This is as per the documentation ( which was updated
as per the comments from [~zjshen]). So it seems like deviating from the last
known purpose and would it break the *compatability* ?
* Whats the point of publishing the ATS events if timeline is not enabled ? it
would unnecessarily populate the RM logs if ATS is not enabled.
* If the main issue is for creation of delegation tokens i would rather prefer
to have some option in the clients to determine whether to create create ATS
delegations tokens or not. Thoughts?
>From ATSV2 team [~sjlee0],[~djp],[~gtCarrera] Any thoughts ?
> Enabling generic application history forces every job to get a timeline
> service delegation token
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-4183
> URL: https://issues.apache.org/jira/browse/YARN-4183
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Mit Desai
> Assignee: Mit Desai
> Fix For: 3.0.0, 2.8.0, 2.7.2
>
> Attachments: YARN-4183.1.patch
>
>
> When enabling just the Generic History Server and not the timeline server,
> the system metrics publisher will not publish the events to the timeline
> store as it checks if the timeline server and system metrics publisher are
> enabled before creating a timeline client.
> To make it work, if the timeline service flag is turned on, it will force
> every yarn application to get a delegation token.
> Instead of checking if timeline service is enabled, we should be checking if
> application history server is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
