hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5257) addBlock() retry should return LocatedBlock with locations else client will get AIOBE
Date Fri, 27 Sep 2013 18:15:02 GMT

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

Colin Patrick McCabe commented on HDFS-5257:
--------------------------------------------

This seems reasonable to me.  It doesn't really make sense for the NN's addBlock to return
a block with no locations to the DFSClient writing a file.

+1.
                
> addBlock() retry should return LocatedBlock with locations else client will get AIOBE
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-5257
>                 URL: https://issues.apache.org/jira/browse/HDFS-5257
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client, namenode
>    Affects Versions: 2.1.1-beta
>            Reporter: Vinay
>            Assignee: Vinay
>            Priority: Critical
>         Attachments: HDFS-5257.patch
>
>
> {{addBlock()}} call retry should return the LocatedBlock with locations if the block
was created in previous call and failover/restart of namenode happened.
> otherwise client will get {{ArrayIndexOutOfBoundsException}} while creating the block
and write will fail.
> {noformat}java.lang.ArrayIndexOutOfBoundsException: 0
> 	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1118)
> 	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1078)
> 	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:511){noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message