[
https://issues.apache.org/jira/browse/MAPREDUCE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253963#comment-13253963
]
Ahmed Radwan commented on MAPREDUCE-4150:
-----------------------------------------
@Robert: Thanks for the suggestion! I agree displaying such information on the
web UI will be very helpful next step. Let's plan on this after we are done
with this ticket so we know exactly what to display.
@ATM: Good point, I filed HADOOP-8280 to take care of that. Thanks!
> 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: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
