[
https://issues.apache.org/jira/browse/HBASE-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1874:
-------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed branch and trunk.
Before committing, I removed the define from HConstants and instead made it an
option you can get from HBaseConfiguration called hbase.meta.scanner.caching.
I set it to 100 rather than 1000 (hope you don't mind Andrei my being
conservative).
Thanks for the patch Andrei.
> 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
> Fix For: 0.20.1, 0.21.0
>
> 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.
