Naganarasimha G R commented on YARN-4368:

Thanks for sharing the views [~sjlee0] & [~vrushalic],
bq. For example, what would we allow in terms of client behavior? Assuming both 
v.1 and v.2 are enabled on the cluster, should clients still have ability to 
pick which version it would write to (e.g. v.1 only, v.2 only, v.1 + v.2)?
Any particular reason for not having the below configurations {{v.1 + v.1.5}} 
or {{v.1.5 + v.2}} ? 

bq. I would lean towards not having it as a client side setting since adhoc 
jobs may choose to not emit stats to ATS v2 and that will disrupt the 
accountability of users on the cluster.
IIUC jobs will just inform from the client side that it will not use the 
timelineservice to emit its events to the ATS but RM & NM's publishers will not 
be impacted with this client configuration. And hence YARN level ATS events 
will be anyway collected.

Given the complexities and the advantages got, my initial opinion would be 
similar to [~vrushalic]'s, just to have one of the versions enabled in the 
cluster at any given point in time.

> Support Multiple versions of the timeline service at the same time
> ------------------------------------------------------------------
>                 Key: YARN-4368
>                 URL: https://issues.apache.org/jira/browse/YARN-4368
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Naganarasimha G R
> During rolling updgrade it will be helpfull to have the older version of the 
> timeline server to be also running so that the existing apps can submit to 
> the older version of ATS .

This message was sent by Atlassian JIRA

Reply via email to