Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <29006005.1173312269380.JavaMail.root@brutus>
Date: Wed, 7 Mar 2007 16:04:29 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1070) Number of racks and datanode double
 temporarily when upgrading from 0.10.1 to 0.11.2
In-Reply-To: <14826617.1173206484071.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478984 ] 

Raghu Angadi commented on HADOOP-1070:
--------------------------------------

>When upgrading from Hadoop 0.10.1 to 0.11.2, I see the number of racks and datanode double after the 2nd startup of the Namenode. 
> After the 3rd startup, they correct themselves:
This is between 0.11.2 and 0.12.x

> Namenode Log After 1st Startup:
> 2007-03-06 18:27:27,045 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 1 racks and 4 datanodes

> Namenode Log After 2nd Startup:
> 2007-03-06 18:27:43,201 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 2 racks and 8 datanodes

Because namenode was restarted before check point in the prev run, both hostName and ip are added to n/w topology. When a datanode is removed in the image or edits log, we dont delete its entry from n/w topo, I am not sure why. Now only ip entries get updated with the new topo info. This explains extra nodes. Now new image is written to disk (equivalent to a checkpoint in the first start up).

>Namenode Log After 3rd Startup:
>2007-03-06 18:28:09,730 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 1 racks and 4 datanodes

Because there at least one checkpoint, we dont see multiple entries.

I am not entirely sure how LOG_DATANODE_REMOVE operation is handled.


> Number of racks and datanode double temporarily when upgrading from 0.10.1 to 0.11.2
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1070
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1070
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.11.2
>            Reporter: Nigel Daley
>         Assigned To: Raghu Angadi
>             Fix For: 0.13.0
>
>
> When upgrading from Hadoop 0.10.1 to 0.11.2, I see the number of racks and datanode double after the 2nd startup of the Namenode.  After the 3rd startup, they correct themselves:
> Namenode Log After 1st Startup:
> 2007-03-06 18:27:27,045 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 1 racks and 4 datanodes
> Namenode Log After 2nd Startup:
> 2007-03-06 18:27:43,201 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 2 racks and 8 datanodes
> Namenode Log After 3rd Startup:
> 2007-03-06 18:28:09,730 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 1 racks and 4 datanodes

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