[
https://issues.apache.org/jira/browse/HBASE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360819#comment-17360819
]
Viraj Jasani commented on HBASE-18298:
--------------------------------------
After removal of RegionCoprocessorEnvironment#getRegionServerServices, (as per
the example provided in ZooKeeperScanPolicyObserver), it seems that coprocs
should create ZKWatcher themselves and share it over "sharedData" map
(RegionCoprocessorEnvironment#getSharedData). And while stopping the coproc, we
need to close watcher. Does this look correct?
Does RegionCoprocessorEnvironment still have some way to utilize ZKWatcher
created by RegionServer directly or it's mandatory for coproc to create it's
own watcher?
FYI [~apurtell]
> RegionServerServices Interface cleanup for CP expose
> ----------------------------------------------------
>
> Key: HBASE-18298
> URL: https://issues.apache.org/jira/browse/HBASE-18298
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Critical
> Fix For: 2.0.0-alpha-4, 2.0.0
>
> Attachments: HBASE-18298.patch, HBASE-18298_V2.patch,
> HBASE-18298_V3.patch, HBASE-18298_V4.patch, HBASE-18298_V5.patch,
> HBASE-18298_V6.patch, HBASE-18298_V7.patch, HBASE-18298_V7.patch
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
