[ 
https://issues.apache.org/jira/browse/HBASE-18571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-18571:
-----------------------------------
    Description: 
HBASE-9534 introduced Short-Circuit coprocessor HTable access when on the same 
server. So when we call Table's method in RegionCP,  if the Table.put(Put) is 
called we will see the old RPC user in the second region call path also. But if 
it was AsyncProcess involved flow, we won't see the old rpc context.

See more detail: 
https://issues.apache.org/jira/browse/HBASE-18500?focusedCommentId=16121630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16121630

> RpcContext inconsistent when call Table's method in 
> RegionCoprocessorEnvironment
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-18571
>                 URL: https://issues.apache.org/jira/browse/HBASE-18571
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Guanghao Zhang
>
> HBASE-9534 introduced Short-Circuit coprocessor HTable access when on the 
> same server. So when we call Table's method in RegionCP,  if the 
> Table.put(Put) is called we will see the old RPC user in the second region 
> call path also. But if it was AsyncProcess involved flow, we won't see the 
> old rpc context.
> See more detail: 
> https://issues.apache.org/jira/browse/HBASE-18500?focusedCommentId=16121630&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16121630



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

Reply via email to