hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-159) Block reports should be processed offline
Date Wed, 18 Jan 2012 09:37:39 GMT

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

Harsh J resolved HDFS-159.

    Resolution: Duplicate

This is a probable duplicate of the resolved HDFS-2379.
> Block reports should be processed offline
> -----------------------------------------
>                 Key: HDFS-159
>                 URL: https://issues.apache.org/jira/browse/HDFS-159
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Owen O'Malley
>            Assignee: Sameer Paranjpye
> The namenode's handling of block reports should be done from a batch queue instead of
while the rpc call from the client is waiting. I'd propose:
>  void blockReport(DataNodeRegistration, Block[]) throws IOException;
> instead of passing back obsolete blocks they can be handed back on later heartbeat.
> The blockReport calls should just queue the registration and list of blocks and there
should be a thread that processes the block reports when possible. 
> The goal is to prevent rpc timeouts and therefore retransmissions of the block lists.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message