Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <258341453.1216181131621.JavaMail.jira@brutus>
Date: Tue, 15 Jul 2008 21:05:31 -0700 (PDT)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3677) Problems with generation stamp
 upgrade
In-Reply-To: <1593061290.1214940525079.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-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raghu Angadi updated HADOOP-3677:
---------------------------------

    Attachment: HADOOP-3677-trunk.patch

Thanks for the review Konstantin.

Attached patches for trunk and 0.18 has the suggested changes and removes GenStamp distributed upgrade. 

The patch is large mainly because it removes around 1000 lines. 3 files are deleted in trunk and one in 0.18.

> Problems with generation stamp upgrade
> --------------------------------------
>
>                 Key: HADOOP-3677
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3677
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.0
>            Reporter: Konstantin Shvachko
>            Assignee: Raghu Angadi
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: HADOOP-3677-branch-018.patch, HADOOP-3677-trunk.patch, HADOOP-3677-trunk.patch
>
>
> # The generation stamp upgrade renames blocks' meta-files so that the name contains the block generation stamp as stated in HADOOP-2656.
> If a data-node has blocks that do not belong to any files and the name-node asks the data-node to remove those blocks 
> during or before the upgrade started the data-node will remove the blocks but not the meta-files because their names 
> are still in the old format which is not recognized by the new code. So we can end up with a number of garbage files which
> will be hard to recognize that they are unused and the system will never remove them automatically.
> I think this should be handled by the upgrade code in the end, but may be it will be right to fix HADOOP-3002 for the 0.18 release,
> which will avoid scheduling block removal when the name-node is in safe-mode.
> # I was not able to get the upgrade -force option to work. This option lets the name-node proceed with a distributed upgrade even if
> the data-nodes are not able to complete their local upgrades. Did we test this feature at all for the generation stamp upgrade?

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