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] [Comment Edited] (HBASE-9864) Notifications bus for use by cluster members keeping up-to-date on changes
Date Mon, 07 Apr 2014 08:26:15 GMT

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

Andrew Purtell edited comment on HBASE-9864 at 4/7/14 8:24 AM:
---------------------------------------------------------------

Not a store for the consensus library, a distributed store/cache for internal use by components
like the security coprocessors and namespace management (all of which currently do their own
thing).

By best effort I proposed above epidemic propagation. We could tune by interval and fanout.
No guarantees besides a likelihood of convergence after an interval that can be derived from
those parameters. 

Yes, another mode that guarantees propagation to all RegionServers or returns failure. 

We could add a simple gossip protocol for the first and use the pluggable distributed barrier
facility for the second. The consensus package could handle the second also.


was (Author: apurtell):
Not a store for the consensus library, a distributed store/cache for internal use by components
like the security coprocessors and namespace management (all of which currently do their own
thing).

By best effort I proposed above epidemic propagation. We could tune by interval and fanout.
No guarantees besides a likelihood of convergence that can be derived from those parameters.


Yes, another mode that guarantees propagation to all RegionServers or returns failure. 

We could add a simple gossip protocol for the first and use the pluggable distributed barrier
facility for the second. The consensus package could handle the second also.

> 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)

Mime
View raw message