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

stack commented on HBASE-19007:
-------------------------------

[~zghaobac] Yes sir. Am on it.

[~ram_krish] and [~anoop.hbase] Thank you lads. Thank you Ram for the 
enumeration. That matches my understanding and shows you are clear on what the 
issue is here. Yeah, its the 'internal' CPs that are causing most problems 
presuming easy access to remote internals. Your suggestion of an internal env 
gave me an idea. Let me see if I can give a particular env to a few 
coprocessors (It might be possible after Appy's recent refactoring).

On Master-side and CPs having access to AM, it looks like most of these cases 
can be replaced with a call to Amin Interface instead ('move', 'tableExists'). 
When Admin Interface is called and the CP is local to the Master, we 
short-circuit RPC and make a direct invocation.

bq. Ya our own CPs is a problem maker in this cleanup effort. These clearly 
suggests we must impl them as core functions (AC, VC etc) 
[~anoop.hbase] Yeah. But hopefully we don't have to do this for 2.0 but can be 
done as follow-on.

Let me add a @CoprocesorAbortException....



> Align Services Interfaces in Master and RegionServer
> ----------------------------------------------------
>
>                 Key: HBASE-19007
>                 URL: https://issues.apache.org/jira/browse/HBASE-19007
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Priority: Blocker
>         Attachments: HBASE-19007.master.001.patch
>
>
> HBASE-18183 adds a CoprocessorRegionServerService to give a view on 
> RegionServiceServices that is safe to expose to Coprocessors.
> On the Master-side, MasterServices becomes an Interface for exposing to 
> Coprocessors.
> We need to align the two.
> For background, see 
> https://issues.apache.org/jira/browse/HBASE-12260?focusedCommentId=16203820&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16203820
>  



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

Reply via email to