[jira] [Commented] (HBASE-21639) maxHeapUsage value not read properly from config during EntryBuffers initialization

["Toshihiro Suzuki (JIRA)" <ji...@apache.org>]

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

Toshihiro Suzuki commented on HBASE-21639:
------------------------------------------

+1

> maxHeapUsage value not read properly from config during EntryBuffers initialization
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-21639
>                 URL: https://issues.apache.org/jira/browse/HBASE-21639
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.3.1, 2.1.0
>            Reporter: Bo Cui
>            Assignee: Pankaj Kumar
>            Priority: Minor
>             Fix For: 3.0.0
>
>         Attachments: HBASE-21639.001.patch
>
>
>  
> {code:java|title=WALSplitter.java|borderStyle=solid}
> entryBuffers = new EntryBuffers(controller,
>  this.conf.getInt("hbase.regionserver.hlog.splitlog.buffersize", 128 * 1024 * 1024),
>  splitWriterCreationBounded);
> {code}
> In above case, EntryBuffers can't support maxHeapUsage in GB size.
> The parameter type of the new EntryBuffers() is long, but the conf max value is INT.MAX. 
> this is wrong？it should be getLong？



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)