You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/01/15 20:21:00 UTC
[jira] [Updated] (HBASE-21639) maxHeapUsage value not read properly
from config during EntryBuffers initialization
[ https://issues.apache.org/jira/browse/HBASE-21639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-21639:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.5
2.1.3
2.2.0
Status: Resolved (was: Patch Available)
Pushed to branch-2.0+ Thanks for patch [~pankaj2461] and for the review [~brfrn169]
> 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, 2.2.0, 2.1.3, 2.0.5
>
> 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)