[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551519#comment-13551519
]
Enis Soztutar commented on HBASE-5487:
--------------------------------------
[~ndimiduk] I guess you won't be working on this for some time, but wanna chime
in the latest status?
Thinking about the use case, what we want is to ensure that client operations
does outlive master failover. Which is why in accumulo/fate, the state is kept
in zk, and the master just provides execution. I think we can achieve the same
thing if we add a WAL for master. Again, we have to break up the operation
(like create table) into adempotent pieces, and sync the WAL before executing
them. On master failover we just have to replay the WAL. Not sure which one
would be simpler though.
> 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
