hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (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 00:00:26 GMT

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

stack commented on HBASE-9864:
------------------------------

Chatting w/ Matteo, would the following do?

+ For namespaces, tags, and ACL, each RS needs to host an up-to-date copy of the table in
its memory.
+ 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.
+ On change, the master ups an internal, in-memory sequence id.
+ When the regionserver heartbeats, currently the response is empty.  Change the Master so
its response is a Set of table names X seqid.
+ When the regionserver gets the heartbeat reply, it checks the seqid.  If any seqids fail
to match, scan the src table and then update the regionserver's seqid to match that of the
master.
+ If the Master crashes, it will reset its seqids.  They won't match the regionservers.  Regionservers
will all rescan (redundantly).

No zk and piggybacking on system we already have in place?

> 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