You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2016/01/22 19:15:40 UTC

[jira] [Updated] (HDFS-9585) Erasure Coding: Wrong limit setting of target ByteBuffer

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

Jing Zhao updated HDFS-9585:
----------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

HDFS-9646 includes the fix. Thanks a lot for reporting the issue and providing the fix, [~lewuathe]!

> Erasure Coding: Wrong limit setting of target ByteBuffer
> --------------------------------------------------------
>
>                 Key: HDFS-9585
>                 URL: https://issues.apache.org/jira/browse/HDFS-9585
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Kai Sasaki
>            Assignee: Kai Sasaki
>              Labels: EC
>         Attachments: HDFS-9585.01.patch
>
>
> In ErasureCodingWorker, target ByteBuffer should be limit by desired recovered size. But due to wrong indexing, an output ByteBuffer does not be limited correctly. 



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