[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010103#comment-15010103
]
Naganarasimha G R commented on YARN-4183:
-----------------------------------------
Thanks for sharing your views [~sjlee0],
bq. I think we should assume a reasonable use case here where it is fair to
expect the timeline service to be there if yarn.timeline-service.enabled is
true. If that config is true but the timeline service is not up, then I think
it is acceptable to see continuous timeline service failures (this is the
existing behavior btw).
Ok even though i am not convinced its 100% necessary but yes i do see benifits
as it will avoid lot logs and delays because of timeline client trying multiple
times for each event being logged.
But along with this i think we need to start the timelineservice daemon only if
*yarn.timeline-service.enabled* is set to true. This will double ensure that
the configurations are done properly. But might have compatability issues.
Thoughts?
bq. I would advocate having a separate client-side config. Whether the server
has enabled the timeline service and whether a particular client/app will use
it are separate concerns, and separate configs should drive them.
I was wondering what should be the default value so that it doesnt break the
compatability with existing apps, i presume it should be true to get the same
behavior as of now ?
> 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)
