[
https://issues.apache.org/jira/browse/HBASE-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093892#comment-13093892
]
Hudson commented on HBASE-4289:
-------------------------------
Integrated in HBase-TRUNK #2160 (See
[https://builds.apache.org/job/HBase-TRUNK/2160/])
HBASE-4289 Move spinlock to SingleSizeCache rather than the slab allocator
(Li Pi)
tedyu :
Files :
* /hbase/trunk/CHANGES.txt
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/io/hfile/slab/SingleSizeCache.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/io/hfile/slab/Slab.java
> Move spinlock to SingleSizeCache rather than the slab allocator.
> ----------------------------------------------------------------
>
> Key: HBASE-4289
> URL: https://issues.apache.org/jira/browse/HBASE-4289
> Project: HBase
> Issue Type: Sub-task
> Reporter: Li Pi
> Assignee: Li Pi
> Priority: Trivial
> Fix For: 0.92.0
>
> Attachments: refactor.diff, refactored.txt
>
>
> The spinlock shouldn't be implemented in the slab allocator, as we don't
> necessarily want to spinlock if we try to request too much memory. Instead,
> null should be returned, and we'll let the user of the slab allocator
> determine what it should do in an OOM situation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
