[
https://issues.apache.org/jira/browse/HDFS-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000625#comment-13000625
]
Jitendra Nath Pandey commented on HDFS-1649:
--------------------------------------------
-1 overall.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 system test framework. The patch failed system test framework compile.
> Federation: Datanode command to refresh namenode list at the datanode.
> ----------------------------------------------------------------------
>
> Key: HDFS-1649
> URL: https://issues.apache.org/jira/browse/HDFS-1649
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: Federation Branch
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Fix For: Federation Branch
>
> Attachments: HDFS-1649.1.patch, HDFS-1649.2.patch, HDFS-1649.4.patch
>
>
> When a namenode is added to or removed from a cluster, we need a way to
> refresh the datanodes:
> 1. Datanode should load new configuration.
> 2. Compares the namenode list it has with that of new configuration. If a
> namenode is deleted, then corresponding
> BPOfferService thread is shutdown. If a new namenode is added, a
> BPOfferService thread is started to service the new
> namenode.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
