[
https://issues.apache.org/jira/browse/YARN-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655062#comment-13655062
]
Karthik Kambatla commented on YARN-666:
---------------------------------------
Sid - thanks for creating this. Excited.
Just went over the design doc (which BTW is well-articulated) and have the
following comments:
# Steps to upgrade a YARN cluster: do you think it would make sense to upgrade
the NMs first before upgrading the RM. If something goes wrong (hopefully not),
users can fall-back to the older version.
# Considerations (Upgrading the MR runtime): Until YARN/MR go into separate
projects and release cycles, upgrading YARN alone (say 2.1.0 to 2.1.2)
shouldn't affect the clients (MR) - no?
# Looks like we need to come up with an appropriate policy for "YARN data
formats" in HADOOP-9517.
# I am assuming the version check will be similar to the one in HDFS-2983.
# Big +1 to "drain decommission"
> [Umbrella] Support rolling upgrades in YARN
> -------------------------------------------
>
> Key: YARN-666
> URL: https://issues.apache.org/jira/browse/YARN-666
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.0.4-alpha
> Reporter: Siddharth Seth
> Attachments: YARN_Rolling_Upgrades.pdf
>
>
> Jira to track changes required in YARN to allow rolling upgrades, including
> documentation and possible upgrade routes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
