[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001607#comment-15001607
]
Naganarasimha G R commented on YARN-4183:
-----------------------------------------
Hi All,
Lately observed there is already a existing configuration
{{"yarn.timeline-service.client.best-effort"}} which ensures even YARNClient
doesnt throw exception even if delegation token fetching fails in
{{YARNClient.SubmitApplication}}. So i feel there is sufficient guard in the
client side when to create Timelineclient and fetch the delegation token and if
fail what action to be taken,
So as part of this jira, as mentioned by [~vinodkv] i think we need to just
remove the check for {{yarn.timeline-service.enable}} being used in
{{SystemMetricsPublisher}} as its a client side configuration (correct me if i
am wrong). And as part of YARN-4234 we are anyway concentrating on how to
support for multiple versions in TimelineClient. right ?
> 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
> 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)
