Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1455713122.1236355196342.JavaMail.jira@brutus>
Date: Fri, 6 Mar 2009 07:59:56 -0800 (PST)
From: "Lei Xu (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4763) Support manually fsck in DataNode
In-Reply-To: <1778369722.1228323824484.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lei Xu commented on HADOOP-4763:
--------------------------------

It depends on several other patches can be accepted or not. like HADOOP-4865

> Support manually fsck in DataNode
> ---------------------------------
>
>                 Key: HADOOP-4763
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4763
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.18.0
>            Reporter: Lei Xu
>             Fix For: 0.21.0
>
>         Attachments: fsck.patch, fsck.patch, HADOOP-4763.patch
>
>
> Now DataNode only support scan all blocks periodically.  Our site need a tool to check some blocks and files manually. 
> My current design is to add a parameter to DFSck to indicate deeply and manually fsck request, then let NameNode collect property block identifies and sent them to associated DataNode. 
> I'll let DataBlockScanner runs in two ways: periodically ( original one ) and manually. 
> Any suggestions on this are welcome. 

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