Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> endpoint coprocessor performance


Copy link to this message
-
Re: endpoint coprocessor performance
I see this is HBASE-6870.  I thought that sounded familiar.
On Mon, Mar 4, 2013 at 6:23 PM, Gary Helmling <[EMAIL PROTECTED]> wrote:

>
> 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.
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB