hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18298) RegionServerServices Interface cleanup for CP expose
Date Tue, 26 Sep 2017 03:42:00 GMT

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

stack commented on HBASE-18298:
-------------------------------

I saw an interesting case today where a CP was being used to keep up a Secondary Index. They
were getting the Table instance from CoprocessorEnvironment which turned into the creation
of a new Connection every time they wanted to put a few edits to the secondary index table.
It was really heavyweight though the 'ordained' way of talking to another table.

If they do their own Connection and connection to ZK, it should be at start of the CP and
keep it around (cache meta locations, etc.). We should write this up or do an example.

Yeah, if they use the RS Connection, could bring the RS down so probably appropriate we not
let them use the RS internal Connection; it aligns w/ the principals being applied to the
CP refactor.

> RegionServerServices Interface cleanup for CP expose
> ----------------------------------------------------
>
>                 Key: HBASE-18298
>                 URL: https://issues.apache.org/jira/browse/HBASE-18298
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>            Priority: Critical
>             Fix For: 2.0.0-alpha-4
>
>         Attachments: HBASE-18298.patch, HBASE-18298_V2.patch, HBASE-18298_V3.patch, HBASE-18298_V4.patch,
HBASE-18298_V5.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message