hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8362) Possible MultiGet optimization
Date Wed, 17 Apr 2013 20:13:18 GMT

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

Lars Hofhansl commented on HBASE-8362:
--------------------------------------

Looking at patch possibilities... A problem is that a reseek can't tell whether it placed
the scanner on an existing row or not, so after each reseek we'd need to do a next even when
the row does not exist.
                
> Possible MultiGet optimization
> ------------------------------
>
>                 Key: HBASE-8362
>                 URL: https://issues.apache.org/jira/browse/HBASE-8362
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>
> Currently MultiGets are executed on a RegionServer in a single thread in a loop that
handles each Get separately (opening a scanner, seeking, etc).
> It seems we could optimize this (per region at least) by opening a single scanner and
issue a reseek for each Get that was requested.
> I have not tested this yet and no patch, but I would like to solicit feedback on this
idea.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message