+1. The patch fixes the original problem I saw.
On Mar 13, 2007, at 10:04 AM, Konstantin Shvachko (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1070?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-1070:
----------------------------------------
Attachment: AddToTopology.patch
The main problem turns out to be that old nodes were considered
alive, and
the name-node was trying to place block replicas on them.
The solution is to add the nodes to the topology map only when they
register.
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: Konstantin Shvachko
Priority: Blocker
Fix For: 0.12.1
Attachments: AddToTopology.patch
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.
