Naganarasimha G R commented on YARN-4183:

Hi [~jeagles],
We are not using ATS at scale you guys are using so you will be the better 
judge  but just my 2 cents  as an observer :
bq. The issue regarding this jira is that putting yarn.timeline-service.enabled 
in the client xml (breaks #2 above) forces every job (both MR (not using 
timeline service) and Tez (using timeline service)) to have a runtime 
dependency on the timeline service.
By having diff configurations for Tez and MR  clients can this problem get 
solved. Or i would prefer rather introducing one more config here which takes 
care of by passing the failure to get delegation tokens. And also as you 
mentioned for soft limit for applications can make use of the same parameter.
bq. 3.YARN services that interact with the timeline server (Generic History 
Server), may have runtime dependency of the timeline service that does not 
disrupt job submission
may be this also we can handle in a different jira if req we can start even if 
timeline client is not up and once up, System Metrics publisher can start 
accepting the timeline events. Thoughts ?
The purpose of "yarn.timeline-service.generic-application-history.enabled" is 
different as per the documentation. so instead we can either remove the check 
for  "TIMELINE_SERVICE_ENABLED" here than check for  
"yarn.timeline-service.generic-application-history.enabled" or create new 
configuration in the client to avoid creation of tokens when not req. 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

Reply via email to