Naganarasimha G R commented on YARN-4183:

Yes, [~sjlee0] & [~gtCarrera], There are too many points to discuss wrt 
versions. But i felt scope of this jira was more on whether to have 
*"yarn.timeline-service.enabled"* is required in RM's SystemMetricsPublisher. 
Which i feel we need to stick to, as viewers of this jira might get confused is 
scope is more . And raise a new jira which can be subtask of 1.5 or 2 and 
discuss the pro's cons of multiple ATS versions to be supported. If OK will 
raise one in 1.5

bq.  I believe it strongly implies it applies to the server-side too. After 
all, even if it is indicated to the client that the timeline service is 
enabled, it would be no use obviously (and actually worse than not indicating) 
if the timeline service was not running. 
Well once we move to 1.5  and 2 we will anyway have some form of 
{{"yarn.timeline-service.version"}} which signify that Server needs to start 
timelineserver and RM's SMP will know whether to publish to timelineserver if 
the version is set.
But as far as 2.7.2 is concerned i feel 
{{yarn.resourcemanager.system-metrics-publisher.enabled}} is sufficient to be 
configured. If not unnecessary additional configuration needs to be done by the 
As far as i view it "yarn.timeline-service.enabled"* name is misleading, it 
should be more to signify client requires the timeline service's delegation 
token. Which will  not be a server side config. 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
>         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

Reply via email to