hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9864) Notifications bus for use by cluster members keeping up-to-date on changes
Date Tue, 08 Apr 2014 15:26:33 GMT

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

Andrew Purtell commented on HBASE-9864:

bq.  When any of these tables are changed, either the editor pokes the Master or the Master
'notices' the change because it is proactively scanning the tables.

This part I'm fuzzy about because currently the coprocessors running on the meta table notice
the change immediately and trigger a notification by changing znode data. How would this work
in the alternative? The reason I suggest a Procedure based update (or equivalent) is so we
can guarantee that the change has committed "immediately" in every local cache, with the additional
benefit of knowing if not. (We don't have this last part today because we use ZK watchers,
but we really should.)

> 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

View raw message