Aaron Gresch commented on YARN-6736:

Is this a dupe of YARN-4368?

We would like to run both services in parallel for a time.  Rather than having 
an "upgrade" mode, I think it would be cleaner to specify the versions in a 
list as mentioned.  I was working on a similar solution to create a publisher 
class that basically took a collection of timeline services to publish to based 
on the versions specified.  

I made a similar change locally and an issue I had was getting my single node 
setup running with both services.  ATS v1 and v2 wanted to use the same port.  
I ended up creating a new conf port setting for v2 that defaults back to the v1 
port if not found.

> Consider writing to both ats v1 & v2 from RM for smoother upgrades
> ------------------------------------------------------------------
>                 Key: YARN-6736
>                 URL: https://issues.apache.org/jira/browse/YARN-6736
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Rohith Sharma K S
>         Attachments: YARN-6736-YARN-5355.001.patch
> When the cluster is being upgraded from atsv1 to v2, it may be good to have a 
> brief time period during which RM writes to both atsv1 and v2. This will help 
> frameworks like Tez migrate more smoothly. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to