[
https://issues.apache.org/jira/browse/MAPREDUCE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653622#comment-13653622
]
Siddharth Seth commented on MAPREDUCE-4150:
-------------------------------------------
Karthik, do you intend to use this jira for work related to MR or YARN ? I'll
create a separate JIRA for YARN / move this one over accordingly. Both are
likely to require some changes.
I have a writeup on YARN rolling upgrades, which I'll post tomorrow. Should be
able to club that along with what you have for rolling upgrades to get this
started.
> Versioning and rolling upgrades for Yarn/MR2
> --------------------------------------------
>
> Key: MAPREDUCE-4150
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4150
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Affects Versions: 0.23.1
> Reporter: Ahmed Radwan
> Assignee: Karthik Kambatla
>
> It doesn't seem that Yarn components, for example the ResourceManager or
> NodeManager, do build/package version checking before trying to communicate
> with each other.
> The objective of this ticket is to support the following requirements / use
> cases:
> - New versions can be marked incompatible with old versions, and services
> should be prevented from communicating with each other in such case. This
> will avoid non-deterministic behavior/problems resulting from incompatible
> components trying to communicate with each other.
> - Permitting a policy for running different - but compatible - versions on
> the same cluster (for example, in a rolling upgrade scenario). See HDFS-2983
> for the corresponding HDFS implementation.
--
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
