hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed Radwan (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MAPREDUCE-4150) Versioning and rolling upgrades for Yarn/MR2
Date Fri, 13 Apr 2012 08:38:16 GMT
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


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

        

Mime
View raw message