You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "surendra singh lilhore (JIRA)" <ji...@apache.org> on 2012/05/16 14:07:02 UTC
[jira] [Commented] (HDFS-3421) ( Dynamic Rack Addition ) : After
adding new Datanode in cluster not possible to change the rack of Datanode
without restarts the Namenode.
[ https://issues.apache.org/jira/browse/HDFS-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276683#comment-13276683 ]
surendra singh lilhore commented on HDFS-3421:
----------------------------------------------
Hi harsh,
thanks for looking this issue.
Yes I do dfsadmin –refreshNodes and for testing i am using 0.24 version.
> ( Dynamic Rack Addition ) : After adding new Datanode in cluster not possible to change the rack of Datanode without restarts the Namenode.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3421
> URL: https://issues.apache.org/jira/browse/HDFS-3421
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Environment: One NameNode and three DataNodes each datanode in diffrent rack
> Reporter: surendra singh lilhore
>
> Scenario:
> I am using the script Mapping Technique for Dynamic Addition of rack.
> 1. Namenode is running with three datanode(xx.xx.xx.45,xx.xx.xx.91,xx.xx.xx.157)
> xx.xx.xx.45 : /datacenter1/rack1
> xx.xx.xx.91 : /datacenter1/rack2
> xx.xx.xx.157 :/datacenter1/rack3
> 2. Stop datanode xx.xx.xx.157.
> 3. change the rack of xx.xx.xx.157 to rack4 in Script file.
> 'xx.xx.xx.45' : '/datacenter1/rack1'
> 'xx.xx.xx.91' : '/datacenter1/rack2'
> 'xx.xx.xx.157' : '/datacenter1/rack4'
> 4. Start datanode xx.xx.xx.157.
> Expected Result : Datanode Should be add in rack4
> Actual Result : Datanode Added in old rack only (rack3).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira