[
https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607754#comment-16607754
]
Hudson commented on HBASE-21166:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #471 (See
[https://builds.apache.org/job/HBase-1.3-IT/471/])
HBASE-21166 Creating a CoprocessorHConnection re-retrieves the cluster (larsh:
rev 386fdb2c3b8712e7f1df179a2deb939bd93cbc5e)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/client/CoprocessorHConnection.java
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionManager.java
> Creating a CoprocessorHConnection re-retrieves the cluster id from ZK
> ---------------------------------------------------------------------
>
> Key: HBASE-21166
> URL: https://issues.apache.org/jira/browse/HBASE-21166
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Major
> Fix For: 1.5.0, 1.3.3, 1.4.8, 1.2.7
>
> Attachments: HBASE-21166.branch-1.001.patch
>
>
> CoprocessorHConnections are created for example during a call of
> CoprocessorHost$Environent.getTable(...). The region server already know the
> cluster id, yet, we're resolving it over and over again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
