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

Anoop Sam John commented on HBASE-19301:
----------------------------------------

bq.A Connection accessing local Server will short-circuit (To be verified).
Not all.  Only the connection created within RS will use this way. A connection 
created at client side (Using ConnectionFactory#createConnection) will NOT use 
the short circuit path. Ya the short circuit removes the RPC things from call. 
It will be a direct stub call.  But we have to do the PB convert. Say when 
mutation happens, all mutations has to be converted to PB and back to Pojo.  
(Some thing to see later how/whether we can avoid this)
bq.But perhaps you are referring to difference between an invocation that goes 
via protobuf service but skips the rpc invocation vs a direct invocation, one 
that skips doing protobuf marshalling/unmarshaling AND rpc?
This is what the short circuit connection doing right?  Are there 2 short 
circuit stuff? I dont know.

> 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.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 server.
> This issue is for providing an overloaded getConnection(Configuration) API



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

Reply via email to