You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Arpit Gupta (JIRA)" <ji...@apache.org> on 2013/08/15 18:44:49 UTC

[jira] [Commented] (AMBARI-2916) DataNode cannot be started on a host that was added post-install

    [ https://issues.apache.org/jira/browse/AMBARI-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741164#comment-13741164 ] 

Arpit Gupta commented on AMBARI-2916:
-------------------------------------

You wont need to restart the namenode. After updating the configs you can run this command as the hdfs super user 'hadoop dfsadmin -refreshNodes'

The same will need to be done for tasktrackers/nodemanagers
                
> DataNode cannot be started on a host that was added post-install
> ----------------------------------------------------------------
>
>                 Key: AMBARI-2916
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2916
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.0
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.4.0
>
>
> The properties for hdfs-site/dfs.hosts and hdfs-site/dfs.hosts.exclude are generated on install (and config change).  When creating a datanode post-install, the files get updated, but requires a restart of the NN in order to for it to read the new entry.  In a normal install, DN should be able to register themselves without any restart.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira