hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3065) Namenode does not process block report if the rack-location script is not provided on namenode
Date Mon, 24 Mar 2008 16:13:24 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581584#action_12581584
] 

Hadoop QA commented on HADOOP-3065:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12378487/3065.patch
against trunk revision 619744.

    @author +1.  The patch does not contain any @author tags.

    tests included -1.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new javac compiler warnings.

    release audit +1.  The applied patch does not generate any new release audit warnings.

    findbugs +1.  The patch does not introduce any new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

    contrib tests +1.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2037/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2037/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2037/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2037/console

This message is automatically generated.

> Namenode does not process block report if the rack-location script is not provided on
namenode
> ----------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3065
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3065
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: Devaraj Das
>             Fix For: 0.17.0
>
>         Attachments: 3065.patch
>
>
> Per HADOOP-1985, If the namenode does not have a dnsToSwicthMapping specified, it does
not process block reports from datanode(s). In the ResolutionMonitor, we have the following
piece of code:
>           List<String> rName = dnsToSwitchMapping.resolve(dnHosts);
>           if (rName == null) {
>             continue;
>           }
> Instead, we should probably set "DEFAULT RACK" for this datanode.
> Also, when a processBlockRepont command is dropped by the namenode, it should log a message
to facilitate debugging. The code in FSNamesystem.processReport could be something like this:
>     if (node.getNetworkLocation().equals(NetworkTopology.UNRESOLVED)) {
>       LOG.info("Ignoring block report from " + nodeID.getName() +
>                       " because rack location for this datanode is still to be resolved.");
>       return null; //drop the block report if the dn hasn't been resolved
>     }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message