You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/08/08 13:48:00 UTC
[jira] [Updated] (HADOOP-14680) Azure: IndexOutOfBoundsException in
BlockBlobInputStream
[ https://issues.apache.org/jira/browse/HADOOP-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-14680:
------------------------------------
Resolution: Fixed
Fix Version/s: 2.9.0
Status: Resolved (was: Patch Available)
> Azure: IndexOutOfBoundsException in BlockBlobInputStream
> --------------------------------------------------------
>
> Key: HADOOP-14680
> URL: https://issues.apache.org/jira/browse/HADOOP-14680
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Reporter: Rajesh Balamohan
> Assignee: Thomas Marquardt
> Priority: Minor
> Fix For: 2.9.0, 3.0.0-beta1
>
> Attachments: HADOOP-14680-001.patch, HADOOP-14680-branch-2.01.patch
>
>
> https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/BlockBlobInputStream.java#L361
> On certain conditions, BlockBlobInputStream can throw IndexOutOfBoundsException. Following is an example
> {{length:297898, offset:4194304, buf.len:4492202, writePos:4194304}} :
> In this case, {{MemoryOutputStream::capacity()}} would end up returning negative value and can cause {{IndexOutOfBoundsException}}
> It should be {{return buffer.length - offset;}} to determine current capacity.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org