[ 
https://issues.apache.org/jira/browse/YARN-4368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014282#comment-15014282
 ] 

Vrushali C commented on YARN-4368:
----------------------------------


This is a good discussion, thanks [~Naganarasimha] for the jira..

Another view for a +1 on this: When there are lightweight users who don't 
really need an hbase-scale timeline data, it would be great to have both 
options available. As yarn adoption is growing, this would be a very useful 
client side feature to have users up and running quickly. 

But, I would rather not have to support both at runtime, would prefer to set up 
one versus the other for the entire cluster. That would help in accounting 
since with a hybrid setup else we can't account for all jobs on the clusters.

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. 




> 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
(v6.3.4#6332)

Reply via email to