Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1405824794.426891269325347541.JavaMail.jira@brutus.apache.org>
Date: Tue, 23 Mar 2010 06:22:27 +0000 (UTC)
From: "Rodrigo Schmidt (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1032) Extend DFSck with an option to list
 corrupt files using API from HDFS-729
In-Reply-To: <875908419.167721268183787985.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HDFS-1032?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12848=
563#action_12848563 ]=20

Rodrigo Schmidt commented on HDFS-1032:
---------------------------------------

The failed contrib test seems to be the same tomcat download error that has=
 haunted other HDFS patches:

{code}
/grid/0/hudson/hudson-slave/workspace/Hdfs-Patch-h2.grid.sp2.yahoo.net/trun=
k/src/contrib/hdfsproxy/build.xml:292: org.codehaus.cargo.container.Contain=
erException:=20
Failed to download [http://apache.osuosl.org/tomcat/tomcat-6/v6.0.18/bin/ap=
ache-tomcat-6.0.18.zip]
{code}

Dhruba, what do you think? Can we commit this one?

> Extend DFSck with an option to list corrupt files using API from HDFS-729
> -------------------------------------------------------------------------
>
>                 Key: HDFS-1032
>                 URL: https://issues.apache.org/jira/browse/HDFS-1032
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>            Reporter: Rodrigo Schmidt
>            Assignee: Andr=C3=A9 Oriani
>         Attachments: hdfs-1032_aoriani.patch, hdfs-1032_aoriani_2.patch
>
>
> HDFS-729 created a new API to namenode that returns the list of corrupt f=
iles.
> We can now extend fsck (DFSck.java) to add an option (e.g. --list_corrupt=
) that queries the namenode using the new API and lists the corrupt blocks =
to the users.

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