Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1508529644.1227571905656.JavaMail.jira@brutus>
Date: Mon, 24 Nov 2008 16:11:45 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4542) Fault in TestDistributedUpgrade
In-Reply-To: <436741870.1225324486570.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Raghu Angadi updated HADOOP-4542:
---------------------------------

    Attachment: HADOOP-4542.patch


Attached simple patch makes {{testDistributedUpgrade()}} a no-op. This easy fix is preferred since :

      - This is going only to 0.18
      - There is  no requirement for DistributedUpgrade in 0.18
      - Already fixed in 0.19 and trunk (not exactly sure by which patch).
      - Even if I fix it (from a patch from 0.19), it is hard for me to reproduce.


> Fault in TestDistributedUpgrade
> -------------------------------
>
>                 Key: HADOOP-4542
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4542
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs, test
>    Affects Versions: 0.18.0
>            Reporter: Robert Chansler
>            Assignee: Raghu Angadi
>            Priority: Minor
>             Fix For: 0.18.3
>
>         Attachments: HADOOP-4542.patch
>
>
> A TestDistributedUpgrade subtest checks that the Name Node _does not_ start when a distributed upgrade is required. In 0.18, the subtest fails when the Name Node _does_ start. The fault is with the test, not HDFS. Not a problem in 0.19.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.