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

Hudson commented on HBASE-5267:
-------------------------------

Integrated in HBase-0.92-security #91 (See 
[https://builds.apache.org/job/HBase-0.92-security/91/])
    HBASE-5267  Add a configuration to disable the slab cache by default (Li 
Pi) (Revision 1241643)

     Result = FAILURE
tedyu : 
Files : 
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/conf/hbase-env.sh
* 
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* /hbase/branches/0.92/src/main/resources/hbase-default.xml

                
> Add a configuration to disable the slab cache by default
> --------------------------------------------------------
>
>                 Key: HBASE-5267
>                 URL: https://issues.apache.org/jira/browse/HBASE-5267
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.92.0
>            Reporter: Jean-Daniel Cryans
>            Assignee: Li Pi
>            Priority: Blocker
>             Fix For: 0.94.0, 0.92.1
>
>         Attachments: 5267.txt, 5267v2.txt, 5267v3.txt, 5267v4.txt
>
>
> From what I commented at the tail of HBASE-4027:
> {quote}
> I changed the release note, the patch doesn't have a "hbase.offheapcachesize" 
> configuration and it's enabled as soon as you set -XX:MaxDirectMemorySize 
> (which is actually a big problem when you consider this: 
> http://hbase.apache.org/book.html#trouble.client.oome.directmemory.leak). 
> {quote}
> We need to add hbase.offheapcachesize and set it to false by default.
> Marking as a blocker for 0.92.1 and assigning to Li Pi at Todd's request.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to