Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <7668647.238461290451755628.JavaMail.jira@thor>
Date: Mon, 22 Nov 2010 13:49:15 -0500 (EST)
From: "Patrick Kling (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1482) Add listCorruptFileBlocks to
 DistributedFileSystem (and ClientProtocol)
In-Reply-To: <10095785.110761288229960764.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934548#action_12934548 ] 

Patrick Kling commented on HDFS-1482:
-------------------------------------

Unfortunately, there is no efficient way of getting the last element of a Collection. So updating lastCookie while doing the iteration is our best bet I think.

> Add listCorruptFileBlocks to DistributedFileSystem (and ClientProtocol)
> -----------------------------------------------------------------------
>
>                 Key: HDFS-1482
>                 URL: https://issues.apache.org/jira/browse/HDFS-1482
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Patrick Kling
>            Assignee: Patrick Kling
>         Attachments: HDFS-1482.2.patch, HDFS-1482.3.patch, HDFS-1482.5.patch, HDFS-1482.patch
>
>
> As discussed in HDFS-1111, it would be beneficial for tools such as the RAID block fixer and RAID FSCK to have access to listCorruptFileBlocks via the DistributedFileSystem (rather than having to parse Servlet output, which could present a performance problem).

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