Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 71D16D561 for ; Thu, 25 Oct 2012 16:53:12 +0000 (UTC) Received: (qmail 74817 invoked by uid 500); 25 Oct 2012 16:53:12 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 74769 invoked by uid 500); 25 Oct 2012 16:53:12 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 74760 invoked by uid 99); 25 Oct 2012 16:53:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 16:53:12 +0000 Date: Thu, 25 Oct 2012 16:53:12 +0000 (UTC) From: "Suresh Srinivas (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1318151037.28118.1351183992113.JavaMail.jiratomcat@arcas> In-Reply-To: <1619756067.18776.1351032371997.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HADOOP-8968) add flag to disable completely version check in the TaskTracker and DataNode MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484271#comment-13484271 ] Suresh Srinivas commented on HADOOP-8968: ----------------------------------------- Alejandro, I can understand skipping version checks in point releases (with the convention - major.minor.point). Skipping the version check in this patch skips it for major and minor releases as well. What is the use case you are trying to address? If it is to allow point releases, should the checks be stricter? Also browsing the code, your log only prints revision when it skipos version check. Should version also be printed? (The names version and revision took me a while to understand :-)) > add flag to disable completely version check in the TaskTracker and DataNode > ---------------------------------------------------------------------------- > > Key: HADOOP-8968 > URL: https://issues.apache.org/jira/browse/HADOOP-8968 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Alejandro Abdelnur > Assignee: Alejandro Abdelnur > Fix For: 1.2.0 > > Attachments: HADOOP-8968.patch, HADOOP-8968.patch > > > The current logic in the TaskTracker and the DataNode to allow a relax version check with the JobTracker and NameNode works only if the versions of Hadoop are exactly the same. > We should add a switch to disable version checking completely, to enable rolling upgrades between compatible versions (typically patch versions). -- 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