[
https://issues.apache.org/jira/browse/MAPREDUCE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla reassigned MAPREDUCE-4150:
-------------------------------------------
Assignee: (was: Karthik Kambatla)
> Versioning and rolling upgrades for 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
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
