You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/08/26 01:10:59 UTC
[jira] [Resolved] (HBASE-11766) Backdoor CoprocessorHConnection is
no longer being used for local writes
[ https://issues.apache.org/jira/browse/HBASE-11766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-11766.
------------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Thanks for the review Ram!
> Backdoor CoprocessorHConnection is no longer being used for local writes
> ------------------------------------------------------------------------
>
> Key: HBASE-11766
> URL: https://issues.apache.org/jira/browse/HBASE-11766
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.4
> Reporter: James Taylor
> Assignee: Andrew Purtell
> Labels: Phoenix
> Fix For: 0.99.0, 2.0.0, 0.98.6
>
> Attachments: HBASE-11766-0.98.patch, HBASE-11766.patch, HBASE-11766.patch
>
>
> There's a backdoor CoprocessorHConnection used to ensure that a batched mutation does not go over the wire and back, but executes immediately locally. This is leveraged by Phoenix during secondary index maintenance (for an ~20% perf improvement). It looks to me like it's no longer used, as the following function is never invoked:
> public org.apache.hadoop.hbase.protobuf.generated.ClientProtos.ClientService.BlockingInterface
> getClient(ServerName serverName) throws IOException {
> It'd be good if feasible to add an HBase unit test to prevent further regressions. For more info, see PHOENIX-1166.
--
This message was sent by Atlassian JIRA
(v6.2#6252)