Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <543524362.1236203036316.JavaMail.jira@brutus>
Date: Wed, 4 Mar 2009 13:43:56 -0800 (PST)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5384) DataNodeCluster should not create
 blocks with generationStamp == 1
In-Reply-To: <886697565.1236127856072.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-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678940#action_12678940 ] 

Tsz Wo (Nicholas), SZE commented on HADOOP-5384:
------------------------------------------------

Yes, it is good to add a new Block constructor.  I think we better to refactor the constructors of Block so that the invalid values can be detected.  How about we do it in a separated JIRA?

> DataNodeCluster should not create blocks with generationStamp == 1
> ------------------------------------------------------------------
>
>                 Key: HADOOP-5384
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5384
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: test
>            Reporter: Tsz Wo (Nicholas), SZE
>         Attachments: 5384_20090303.patch
>
>
> In DataNodeCluster.main(..), injected blocks are created with generationStamp == 1, which is a reserved value but not a valid generation stamp.  As a consequence, NameNode may die when those blocks are reported.

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