[ https://issues.apache.org/jira/browse/HBASE-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777800#comment-13777800 ]
Himanshu Vashishtha commented on HBASE-9534: -------------------------------------------- The point is the code is different in 96 and trunk now. Looks like different patches were committed? See ctr chaining in HTable, for example. > 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