[
https://issues.apache.org/jira/browse/YARN-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16121505#comment-16121505
]
Rohith Sharma K S commented on YARN-6736:
-----------------------------------------
Thanks [~agresch] for your comments! On behalf of YARN community, I welcome you
to YARN project and appreciate your interest on contribution.
bq. Is this a dupe of YARN-4368?
Probably Yes!
bq. I think it would be cleaner to specify the versions in a list as mentioned.
make sense to me as well! Primary reason to add upgrade config is this required
during upgrades only. If a user starting freshly, directly he can make use of
V2. V2 support all V1 use case as well as well many more things wrt scalability
and other. Life long running both servers, I do not think it is really optimal
deployment strategy.
bq. 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 wasn't known that you also working on this JIRA. Probably what you could do
is, comment on the JIRA so that others won't take it up. Would you like to work
on this JIRA? Feel free to take it up, I can help you in reviewing and
committing patch.
bq. 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.
Yeah, this is problem in cluster manager such as Ambari. This need to be fixed.
We use same config for both V1 and V2 reader daemon.
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
