[
https://issues.apache.org/jira/browse/HBASE-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778408#comment-13778408
]
Hudson commented on HBASE-9534:
-------------------------------
FAILURE: Integrated in hbase-0.96 #95 (See
[https://builds.apache.org/job/hbase-0.96/95/])
HBASE-9658: Addendum to HBASE-9534 to fix 0.96 (jyates: rev 1526334)
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Short-Circuit Coprocessor HTable access when on the same server
> ---------------------------------------------------------------
>
> Key: HBASE-9534
> URL: https://issues.apache.org/jira/browse/HBASE-9534
> Project: HBase
> Issue Type: Bug
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Labels: coprocessors, performance, regionserver
> Fix For: 0.98.0, 0.94.12, 0.96.0
>
> Attachments: 9534-trunk.txt, hbase-9534-0.94-v0.patch,
> hbase-9534-0.94-v1.patch, hbase-9534-0.94-v2.patch,
> hbase-9534-trunk-v0.patch, hbase-9534-trunk-v1.patch,
> hbase-9534-trunk-v2.patch
>
>
> Coprocessors currently create a full HTable when they want to write. However,
> we know that coprocessors must run from within an HBase server (either master
> or RS). For the master, its rare that we are going to be doing performance
> sensitive operations, but RS calls could be very time-intensive.
> Therefore, we should be able to tell when a call from a CP attempts to talk
> to the RS on which it lives and just short-circuit to calling that RS, rather
> than going the long way around (which does the full marshalling/unmarshalling
> of data, as well as going over the loopback interface).
--
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
