hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8233) Fix DFSStripedOutputStream#getCurrentBlockGroupBytes when the last stripe is at the block group boundary
Date Wed, 30 Sep 2015 16:02:16 GMT

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

Hudson commented on HDFS-8233:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #8548 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8548/])
HDFS-8233. Fix DFSStripedOutputStream#getCurrentBlockGroupBytes when the (zhezhang: rev eb612b0b70f1439194d3c1cdf151f3301e88522b)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSStripedOutputStream.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES-HDFS-EC-7285.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSStripedOutputStream.java


> Fix DFSStripedOutputStream#getCurrentBlockGroupBytes when the last stripe is at the block
group boundary
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8233
>                 URL: https://issues.apache.org/jira/browse/HDFS-8233
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>             Fix For: HDFS-7285
>
>         Attachments: hdfs8233-HDFS-7285.000.patch
>
>
> Currently {{DFSStripedOutputStream#getCurrentBlockGroupBytes}} simply uses {{getBytesCurBlock}}
of each streamer to calculate the block group size. This is wrong when the last stripe is
at the block group boundary, since the {{bytesCurBlock}} is set to 0 if an internal block
is finished.
> For example, when the real block size is {{blockGroupSize - cellSize * (numDataBlocks
- 1)}}, i.e., the first internal block is full while the others are not, the {{getCurrentBlockGroupBytes}}
returns wrong result and cause the write to fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message