hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5000) Speed up simultaneous reads of a block when block caching is turned off
Date Mon, 12 Dec 2011 20:23:31 GMT

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

Hudson commented on HBASE-5000:
-------------------------------

Integrated in HBase-TRUNK-security #29 (See [https://builds.apache.org/job/HBase-TRUNK-security/29/])
    HBASE-5000 Speed up simultaneous reads of a block when block caching is turned off; bit
of doc and why its a bad idea disabling block cache completely

stack : 
Files : 
* /hbase/trunk/src/docbkx/configuration.xml

                
> Speed up simultaneous reads of a block when block caching is turned off
> -----------------------------------------------------------------------
>
>                 Key: HBASE-5000
>                 URL: https://issues.apache.org/jira/browse/HBASE-5000
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>            Priority: Minor
>
> With block caching, when one client starts reading a block and another one comes around
asking for the same block, the second client waits for the first one to finish reading and
returns the block from cache. This is achieved by locking on the block offset using IdLock,
a "sparse lock" primitive allowing to lock on arbitrary long numbers. However, in case there
is no block caching, there is no reason to wait for other clients that are reading the same
block. One challenge optimizing this that we don't necessary have accurate information about
whether other HFile API clients interested in the block would cache it.
> Setting priority as minor, as it is very unusual to turn off block caching.

--
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

        

Mime
View raw message