You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2013/04/17 20:55:15 UTC

[jira] [Commented] (HBASE-8362) Possible MultiGet optimization

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

Nicolas Liochon commented on HBASE-8362:
----------------------------------------

I expect it will be much better. My only concern I have is for sparse multigets when there are a lot of regions. We may hit some servers that we would not hit with the current approach, with the risk of going to a slow/dead server. So doing the optimization per region would solve this specific case (or doing it per region server only).
                
> 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