Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <308368910.1213844505030.JavaMail.jira@brutus>
Date: Wed, 18 Jun 2008 20:01:45 -0700 (PDT)
From: "Nigel Daley (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Resolved: (HADOOP-1979) fsck on namenode without datanodes
 takes too much time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nigel Daley resolved HADOOP-1979.
---------------------------------

    Resolution: Fixed

> 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.17.1
>            Reporter: Koji Noguchi
>            Assignee: Lohit Vijayarenu
>            Priority: Minor
>             Fix For: 0.17.1
>
>         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.