Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 10 May 2013 08:35:17 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12550798.1334306188695.298679.1368174917632@arcas>
In-Reply-To: <JIRA.12550798.1334306188695@arcas>
References: <JIRA.12550798.1334306188695@arcas>
Subject: [jira] [Commented] (MAPREDUCE-4150) Versioning and rolling upgrades
 for Yarn/MR2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653638#comment-13653638 ] 

Karthik Kambatla commented on MAPREDUCE-4150:
---------------------------------------------

Hi Sid

Thanks for reaching out. I have some ideas, but haven't had a chance to work on it. Agree we will need changes in both YARN and MR. Please go ahead and create a YARN JIRA to address the YARN part, keen to see your write up and contribute.
                
> 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