[
https://issues.apache.org/jira/browse/HADOOP-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589799#action_12589799
]
Hadoop QA commented on HADOOP-1979:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12380340/HADOOP-1979.patch
against trunk revision 645773.
@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/2257/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2257/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2257/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2257/console
This message is automatically generated.
> fsck on namenode without datanodes takes too much time
> ------------------------------------------------------
>
> Key: HADOOP-1979
> URL: https://issues.apache.org/jira/browse/HADOOP-1979
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Koji Noguchi
> Assignee: lohit vijayarenu
> Priority: Minor
> Fix For: 0.18.0
>
> Attachments: HADOOP-1979.patch
>
>
> Once in a while , we want to debug by bringing up the namenode without any
> datanodes. dfs -ls/-lsr works, but fsck / takes too much time. (at least 10
> times more) Most likely from HADOOP-943 that I requested. If this is the
> case, it would be nice if we can have an option for disabling it for this
> special case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
