Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 11 Sep 2014 03:28:34 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12740672.1410405884000.6335.1410406114042@Atlassian.JIRA>
In-Reply-To: <JIRA.12740672.1410405884000@Atlassian.JIRA>
References: <JIRA.12740672.1410405884000@Atlassian.JIRA>
 <JIRA.12740672.1410405884120@arcas>
Subject: [jira] [Updated] (MAPREDUCE-6084) Load MR Configuration from
 distributed cache rather than individual node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du updated MAPREDUCE-6084:
----------------------------------
    Attachment: Compatibility of Configuration Across Different MR Versions.pdf

> Load MR Configuration from distributed cache rather than individual node
> ------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6084
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6084
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>         Attachments: Compatibility of Configuration Across Different MR Versions.pdf
>
>
> For rolling upgrade YARN & MapReduce component, we already support to submit jobs against different versions of mapreduce jars based on distributed cache (please refer MAPREDUCE-4421). However, this could bring up some potential issues if old jar cannot find a new added class with new configurations that upgrade together with Hadoop components. For details, please refer the proposal in attachments. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)