hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1058) reading from file under construction fails if it reader beats writer to DN for new block
Date Mon, 22 Mar 2010 00:57:27 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848013#action_12848013

Todd Lipcon commented on HDFS-1058:

Error looks something like this:

Caused by: java.io.IOException: Cannot obtain block length for LocatedBlock{blk_-6324096824609457750_1001;
                 corrupt=false; offset=0; locs=[]}
2010-03-21 16:46:49,825 DEBUG hdfs.DFSClient (DFSInputStream.java:readBlockLength(152)) -
Faild to getReplicaVisibleLength from 
                 datanode for block blk_-6324096824609457750_1001
org.apache.hadoop.ipc.RemoteException: org.apache.hadoop.hdfs.server.datanode.ReplicaNotFoundException:
Replica not found for 

> reading from file under construction fails if it reader beats writer to DN for new block
> ----------------------------------------------------------------------------------------
>                 Key: HDFS-1058
>                 URL: https://issues.apache.org/jira/browse/HDFS-1058
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, hdfs client
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
> If there is a writer and concurrent reader, the following can occur:
> - The writer allocates a new block from the NN
> - The reader calls getBlockLocations
> - Reader connects to the DN and calls getReplicaVisibleLength
> - writer still has not talked to the DN, so DN doesn't know about the block and throws
an error

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

View raw message