[
https://issues.apache.org/jira/browse/HADOOP-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613128#action_12613128
]
Hadoop QA commented on HADOOP-3720:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385669/HADOOP-3720-3.patch
against trunk revision 676069.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 appears to introduce 2 new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2847/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2847/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2847/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2847/console
This message is automatically generated.
> dfsadmin -refreshNodes should re-read the config file.
> ------------------------------------------------------
>
> Key: HADOOP-3720
> URL: https://issues.apache.org/jira/browse/HADOOP-3720
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.19.0
> Reporter: Lohit Vijayarenu
> Assignee: Lohit Vijayarenu
> Attachments: HADOOP-3720-1.patch, HADOOP-3720-2.patch,
> HADOOP-3720-3.patch
>
>
> hadoop dfsadmin -refreshNodes reads files defined by _dfs.hosts_ and
> _dfs.hosts.exclude_. If these values are not defined during namenode startup,
> then refreshNodes command assumes there are no files. So, while namenode is
> running, once cannot just edit the config file and add entries to these
> config variables and expect the namenode to read them. Namenode should
> re-read the config file for these variables (_dfs.hosts_ and
> _dfs.hosts.exclude_) when refreshNodes command is invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
