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

Naganarasimha G R commented on YARN-4368:
-----------------------------------------

My thoughts :
*Pros :* 
* Continiously busy cluster it would be helpfull to have this feature as 
propability of bringing down the old ATS version and starting new will be less
* May be all apps have not migrated to the new ATS version's client API's.

*Cons :*
* RM's SMP need to publish for both ATS ? or only to the latest one ? if both 
unnecessary load but if only to latest then all informations are not available 
for the existing apps.
* AHS should be able to pick the data from both versions based on the previous 
conclusion !
* User might get confused which ATS configs to use and how long it will be 
supported  and whether all information will be supported from all versions!
* If its for momentary down time, would working on this be good ROI ?


> 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