hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Helmling <ghelml...@gmail.com>
Subject Re: endpoint coprocessor performance
Date Tue, 05 Mar 2013 02:23:43 GMT
> Check your logs for whether your end-point coprocessor is hitting
> zookeeper on every invocation to figure out the region start key.
> Unfortunately (at least last time I checked), the default way of invoking
> an end point coprocessor doesn't use the meta cache. You can go through a
> combination of the following instead:
>     HRegionLocation regionLocation = retried ?
>         connection.relocateRegion(**tableName, tableKey) :
>         connection.locateRegion(**tableName, tableKey);
>     ...
> Then call HConnection.processExecs call, passing in the regionKeys from
> above.
> You can trap the error case of the region being relocated and try again
> with retried = true and it'll update the meta data cache when
> relocateRegion is called.

Any idea if we have an improvement logged in JIRA for this?  This is
definitely something we should improve on.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message