[
https://issues.apache.org/jira/browse/HBASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611365#action_12611365
]
stack commented on HBASE-723:
-----------------------------
Jb Lee:
Thanks for filing the issue.
Its correct to mark it minor I think. Here's why. This is the declaration for
cachedRegionLocation:
{code}
private final Map<Integer, SoftSortedMap<byte [], HRegionLocation>>
cachedRegionLocations = ....
{code}
Its a map of integer keys to a value that is a map of soft references. If
pressure on memory in the client, while the keys are hard references, the map
of the much bigger soft references will release its hold on region locations.
It could be a problem when we hit extremely large tables.
Andrew: Good find. Make another issue for it?
> TableServers's cachedRegionLocation doesn't have size limit.
> ------------------------------------------------------------
>
> Key: HBASE-723
> URL: https://issues.apache.org/jira/browse/HBASE-723
> Project: Hadoop HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.1.3
> Environment: hbase 0.3.0
> Reporter: Jb Lee
> Assignee: Andrew Purtell
> Priority: Minor
>
> cachedRegionLocation stores region locations of tables whenever new region is
> looked up. However, the enties are deleted only when TableServers object is
> closed or locateRegion is called with false useCache argument. Therefore, it
> seems to grow without limit and cause out of memory exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
