hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19301) Provide way for CPs to create short circuited connection with custom configurations
Date Wed, 06 Dec 2017 05:28:01 GMT

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

Anoop Sam John commented on HBASE-19301:

On removing the getConnection() - the issue is our CPs like AC etc are making heavy use of
them?  We have a CoreCoprocessor way and passing a special RegionEnvironment to them.  We
have getRegionServerServices() extra there.  Whether this RegionServerServices having a getConnection()
which gives the HRS connection will work?
Ya with warn expose to CPs is fine. But better do not ?
Ya createConnection() always create new connection. The concern of too many cons is valid.
But till 1.x we have only this way. There were no getConnection() stuff which return shared
connection.  The head ache of caching/sharing the connection was with CPs. Phoenix and all
do that already.  Just like client side how users handle. The only diff of createConnection()
here is it gives a short circuited connection. Else same as con created using ConnectionFactory..
Ya lets see how/what solution comes up for the other issue of user and sharing the RPC context.
I believe [~zghaobac] working on that. (?)

> Provide way for CPs to create short circuited connection with custom configurations
> -----------------------------------------------------------------------------------
>                 Key: HBASE-19301
>                 URL: https://issues.apache.org/jira/browse/HBASE-19301
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0-beta-1
>         Attachments: HBASE-19301-addendum.patch, HBASE-19301.patch, HBASE-19301_V2.patch,
> Over in HBASE-18359 we have discussions for this.
> Right now HBase provide getConnection() in RegionCPEnv, MasterCPEnv etc. But this returns
a pre created connection (per server).  This uses the configs at hbase-site.xml at that server.

> Phoenix needs creating connection in CP with some custom configs. Having this custom
changes in hbase-site.xml is harmful as that will affect all connections been created at that
> This issue is for providing an overloaded getConnection(Configuration) API

This message was sent by Atlassian JIRA

View raw message