[
https://issues.apache.org/jira/browse/HBASE-19077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239918#comment-16239918
]
Anoop Sam John commented on HBASE-19077:
----------------------------------------
We have a problem here. OnlineRegions extending Server. So we are exposing
Server interface also. It will be dangerous to expose all the APIs in server
to CPs. Even the RS can be aborted. It exposes ChoreService,
CoordinatedStateManager , ZooKeeperWatcher etc which should not be ideally. At
Master CP side , we are not exposing the Server.
We can change OnlineRegions not to extend Server. Let the RegionServerServices
only extend Server. We can do it as an addendum here or need a new issue?
[~stack]
> Have Region*CoprocessorEnvironment provide an ImmutableOnlineRegions
> --------------------------------------------------------------------
>
> Key: HBASE-19077
> URL: https://issues.apache.org/jira/browse/HBASE-19077
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
> Reporter: stack
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-19077.master.001.patch,
> HBASE-19077.master.002.patch
>
>
> This is about restoring some of the hbase1 parity... You used to be able to
> get list of Region on the local server and talk to them directly.
> Suggested by [~anoop.hbase] up in review. Makes sense.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
