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

Jesse Yates commented on HBASE-5487:
------------------------------------

I think using the WAL is not the ideal mechanism; it makes master failover a 
very heavy-weight operation (requires WAL replay) and it makes it really hard 
to reason about what changes should be replicated to the target clusters and 
which shouldn't (maybe one cluster mirrors prod, but the other is stores 2x 
history). 

We already require ZK to be up and store an awful amount of state up there to 
the point where we are hurting if we don't have it (particularly replication).

An idea that [~ctrezzo] just proposed (and I really like) is to move this to a 
'system level table'. Since we don't lose data in HBase, we can be sure it 
survives master failover, but has approaching zero MTTR and maintains our 
current invariants. Only problem is the added complexity :)
                
> Generic framework for Master-coordinated tasks
> ----------------------------------------------
>
>                 Key: HBASE-5487
>                 URL: https://issues.apache.org/jira/browse/HBASE-5487
>             Project: HBase
>          Issue Type: New Feature
>          Components: master, regionserver, Zookeeper
>    Affects Versions: 0.94.0
>            Reporter: Mubarak Seyed
>            Assignee: Nick Dimiduk
>
> Need a framework to execute master-coordinated tasks in a fault-tolerant 
> manner. 
> Master-coordinated tasks such as online-scheme change and delete-range 
> (deleting region(s) based on start/end key) can make use of this framework.
> The advantages of framework are
> 1. Eliminate repeated code in Master, ZooKeeper tracker and Region-server for 
> master-coordinated tasks
> 2. Ability to abstract the common functions across Master -> ZK and RS -> ZK
> 3. Easy to plugin new master-coordinated tasks without adding code to core 
> components

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to