[HBASE-9864] Notifications bus for use by cluster members keeping up-to-date on changes

• Type: Brainstorming
• Status: Closed
• Priority: Blocker
• Resolution: Won't Fix
• Tags: architecture service
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 30/Oct/13 20:03
• Updated: 15/Jun/22 17:31
• Resolved: 12/Jun/22 00:04

Description

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?

Issue Links

• is duplicated by: HBASE-7254 Refactor AccessController ZK-mediated permissions cache into a generic mechanism
• is related to: HBASE-10295 Refactor the replication implementation to eliminate permanent zk node
• is related to: HBASE-10919 [VisibilityController] ScanLabelGenerator using LDAP
• is related to: HBASE-11608 Add synchronous split
• is related to: HBASE-10909 Abstract out ZooKeeper usage in HBase - phase 1
• relates to: HBASE-9426 Make custom distributed barrier procedure pluggable
• relates to: HBASE-10544 Surface completion state of global administrative actions