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-12884) Asynchronous Event Notification in HBase
Date Tue, 20 Jan 2015 17:54:35 GMT

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

Andrew Purtell commented on HBASE-12884:
----------------------------------------

bq. Transform the WAL edits to events, and replicates a special peer that users implements.

I like it! With pluggable replication endpoints, setting it up could be as simple as specifying
the event notification replication source class in add_peer and use of a small client library
for users that handles the housework of a replication sink. 

>  Asynchronous Event Notification in HBase
> -----------------------------------------
>
>                 Key: HBASE-12884
>                 URL: https://issues.apache.org/jira/browse/HBASE-12884
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Liu Shaohui
>
> *Background*
> In many scenarios, we need an asynchronous event notification 
> mechanism on HBase to know which data have been changed and users can do some pre-defined
reactions to these events.
> For example: 
> * Incremental statistics of data in HBase
> * Audit about change of important data
> * To clean invalid data in other cache systems
> *Features maybe*
> * The mechanism is scalable.
> * The notification is asynchronous. We don't want to affect the write performance of
HBase.
> * The notification is reliable. The events can't be lost, but we can tolerate duplicated
events.
> *Solution Maybe*
> * Event notification based on replication. Transform the WAL edits to events, and replicates
a special peer that users implements.
> This is just a brief thought about this feature. Discussions and suggestions are welcomed!
Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message