[ 
https://issues.apache.org/jira/browse/HBASE-21166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16606739#comment-16606739
 ] 

Hadoop QA commented on HBASE-21166:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue}  0m  
2s{color} | {color:blue} The patch file was not named according to hbase's 
naming conventions. Please see 
https://yetus.apache.org/documentation/0.7.0/precommit-patchnames for 
instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HBASE-21166 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-21166 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12938741/21166-1.5.txt |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/14342/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>         Attachments: 21166-1.5.txt
>
>
> 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)

Reply via email to