You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2018/09/07 00:25:00 UTC

[jira] [Commented] (HBASE-21166) Creating a CoprocessorHConnection re-retrieves the cluster id from ZK

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

Lars Hofhansl commented on HBASE-21166:
---------------------------------------

Simple 1.5 fix. Just uses the cluster the server already knows (and if that is null - as it could be in tests - it uses the normal retrieval process).

> 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
>            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)