[
https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607991#comment-16607991
]
Hudson commented on HBASE-21166:
--------------------------------
Results for branch branch-1.3
[build #458 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/458/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/458//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/458//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.3/458//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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)
