hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1874) Client Scanner mechanism that is used for HbaseAdmin methods (listTables, tableExists), is very slow if the client is far away from the HBase cluster
Date Tue, 29 Sep 2009 17:58:17 GMT

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

Andrew Purtell commented on HBASE-1874:
---------------------------------------

Makes sense for MetaScanner to use caching in general.

+1


> Client Scanner mechanism that is used for HbaseAdmin methods (listTables, tableExists),
is very slow if the client is far away from the HBase cluster
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1874
>                 URL: https://issues.apache.org/jira/browse/HBASE-1874
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.0
>            Reporter: Andrei Dragomir
>            Priority: Minor
>         Attachments: HBASE-1874.patch
>
>
> I have a simple class that instantiates an HBaseAdmin object, and tries to connect to
a remote hbase cluster (latency about 300ms). 
> When doing any kind of simple operation, like listTables, tableExists, it takes a huge
amount of time, because the mechanism is to instantiate a scanner on the client, so for each
row in the .META. table, we get a client - cluster roundtrip. This is prohibitive in the case
of a far away client. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message