accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2671) BlockedOutputStream can hit a StackOverflowError
Date Fri, 18 Apr 2014 14:41:19 GMT

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

ASF subversion and git services commented on ACCUMULO-2671:
-----------------------------------------------------------

Commit 05507206410bc289da98bfb7931d1cea43cc69a2 in accumulo's branch refs/heads/1.6.0-SNAPSHOT
from [~vines]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=0550720 ]

ACCUMULO-2671 adjusting test to make jenkins happy


> BlockedOutputStream can hit a StackOverflowError
> ------------------------------------------------
>
>                 Key: ACCUMULO-2671
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2671
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Jonathan Park
>            Assignee: John Vines
>             Fix For: 1.6.1, 1.7.0
>
>
> This issue mostly came up after a resolution to ACCUMULO-2668 that allows a byte[] to
be passed directly to the underlying stream from the NoFlushOutputStream.
> The problem appears to be due to the BlockedOutputStream.write(byte[], int, int) implementation
that recursively writes out blocks/buffers out. When the stream is passed a large mutation
(128MB was sufficient to trigger the error for me), this will cause a StackOverflowError.

> This is appears to be specifically with encryption at rest turned on.
> A simple fix would be to unroll the recursion.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message