[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999811#comment-14999811
]
Naganarasimha G R commented on YARN-4183:
-----------------------------------------
Thanks [~vinodkv] and [~gtCarrera], for clarifications for the approach.
Few more clarifications i would like to have :
* How to support backward compatability for existing users who are already
using *yarn.timeline-service.enabled* to get the tokens.
* Do we need to support the use cases which were mentioned by Jonathan,
*# Suport Soft limit and hard settings for the clients : dont throw any
exception if not able get timeline delegation token and may be job should be
still be able to progress.
*# If the creation of the timelineclient based on this new
{{yarn.timeline-service.version}} fails, then do we need to stop the RM ? or
just keep on trying and once its able to contact then start pushing the system
metrics events ?
[~gtCarrera],
bq. I can open a new subtask in YARN-2928 to fix this for V2.
Already Subtask YARN-3623 is raised for this, hope i can work on this ?
> 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)
