[
https://issues.apache.org/jira/browse/HBASE-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-9864:
----------------------------------
Priority: Blocker (was: Major)
Fix Version/s: 1.0.0
With the namespace auditor we have yet another ZK based cache+notification bus
possibly going in. At some point we have to stop reimplementing variations of
this and pay down the accumulating technical debt. It's not fair to require a
contributor to do that work along with what they actually want to accomplish,
but at some point we have to deal with this. Is 1.0 a reasonable line in the
sand? I have set this as a blocker for that release to stimulate some
discussion.
> Notifications bus for use by cluster members keeping up-to-date on changes
> --------------------------------------------------------------------------
>
> Key: HBASE-9864
> URL: https://issues.apache.org/jira/browse/HBASE-9864
> Project: HBase
> Issue Type: Brainstorming
> Reporter: stack
> Priority: Blocker
> Fix For: 1.0.0
>
>
> In namespaces and acls, zk callbacks are used so all participating servers
> are notified when there is a change in acls/namespaces list.
> The new visibility tags feature coming in copies the same model of using zk
> with listeners for the features' particular notifications.
> Three systems each w/ their own implementation of the notifications all using
> zk w/ their own feature-specific watchers.
> Should probably unify.
> Do we have to go via zk? Seems like all want to be notified when an hbase
> table is updated. Could we tell servers directly rather than go via zk?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
