accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4716) Do not attempt to cache blocks over max array size
Date Thu, 12 Oct 2017 23:27:00 GMT


Christopher Tubbs commented on ACCUMULO-4716:

Should this issue be closed now? I believe the fixVersion should be 1.7.4, 1.8.2, and 2.0.0.
Please verify and update JIRA.

> Do not attempt to cache blocks over max array size
> --------------------------------------------------
>                 Key: ACCUMULO-4716
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>            Assignee: Mark Owens
>              Labels: newbie, pull-request-available
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
> One might think you could do {{new byte\[Integer.MAX_VALUE\]}} in Java, but as I found
when looking into ACCUMULO-4708 *suprise* you can't.  
> According to the [stack overflow post |] {{new byte\[Integer.MAX_VALUE
- 8\]}} should be safe.  I was able to do up to {{new byte\[Integer.MAX_VALUE - 2\]}} in my
local testing.
> When Accumulo caches a block it reads it into a byte array.  For example this code in
does this when {{_currBlock.getRawSize() <= cache.getMaxSize()}}.
> This code should ensure the size is less than {{min( cache.getMaxSize(), MAX_ARRAY_SIZE)}}
inorder to read it into a byte array.

This message was sent by Atlassian JIRA

View raw message