Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 4AD194B6D for ; Fri, 27 May 2011 10:15:31 +0000 (UTC) Received: (qmail 58646 invoked by uid 500); 27 May 2011 10:15:31 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 58620 invoked by uid 500); 27 May 2011 10:15:31 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 58612 invoked by uid 99); 27 May 2011 10:15:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2011 10:15:31 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2011 10:15:28 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 112A6E2080 for ; Fri, 27 May 2011 10:14:48 +0000 (UTC) Date: Fri, 27 May 2011 10:14:48 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1992433179.48333.1306491288066.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-107) Data-nodes should be formatted when the name-node is formatted. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040164#comment-13040164 ] ramkrishna.s.vasudevan commented on HDFS-107: --------------------------------------------- Can we provide a config parameter saying 'datanode.format.required' If this value is set to true, whenever the DN starts we can update the DN namespace id with the NN namespace id. If the value is set to false then we can continue with the existing behvaiour. Kindly provide your comments. > Data-nodes should be formatted when the name-node is formatted. > --------------------------------------------------------------- > > Key: HDFS-107 > URL: https://issues.apache.org/jira/browse/HDFS-107 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Konstantin Shvachko > > The upgrade feature HADOOP-702 requires data-nodes to store persistently the namespaceID > in their version files and verify during startup that it matches the one stored on the name-node. > When the name-node reformats it generates a new namespaceID. > Now if the cluster starts with the reformatted name-node, and not reformatted data-nodes > the data-nodes will fail with > java.io.IOException: Incompatible namespaceIDs ... > Data-nodes should be reformatted whenever the name-node is. I see 2 approaches here: > 1) In order to reformat the cluster we call "start-dfs -format" or make a special script "format-dfs". > This would format the cluster components all together. The question is whether it should start > the cluster after formatting? > 2) Format the name-node only. When data-nodes connect to the name-node it will tell them to > format their storage directories if it sees that the namespace is empty and its cTime=0. > The drawback of this approach is that we can loose blocks of a data-node from another cluster > if it connects by mistake to the empty name-node. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira