[
https://issues.apache.org/jira/browse/HBASE-9983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824869#comment-13824869
]
Hudson commented on HBASE-9983:
-------------------------------
SUCCESS: Integrated in hbase-0.96 #192 (See
[https://builds.apache.org/job/hbase-0.96/192/])
HBASE-9983 Lower the memory footprint of HRegionLocation (nkeywal: rev 1542696)
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionLocation.java
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/AsyncProcess.java
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java
> Lower the memory footprint of HRegionLocation
> ---------------------------------------------
>
> Key: HBASE-9983
> URL: https://issues.apache.org/jira/browse/HBASE-9983
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.96.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9983.v2.patch, unbloated.patch
>
>
> It"s more or less a desperate cause...
> If we have a lot of regions, the size of this class becomes a problem. It's
> under optimized for this case...
> This patch is just about the trivial part
--
This message was sent by Atlassian JIRA
(v6.1#6144)
