[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556709#comment-13556709
]
Enis Soztutar commented on HBASE-5487:
--------------------------------------
bq. Is there any chance we could get a high level design deck/doc that
illustrates these processes currently and what looks like after we move to this
proposed FATE-like mechanism? Also, what operations would eventually get ported
to this mechanism? I think discussion and an example at the design/rpc comms
level would help a whole lot by grounding this conversion in reality and not
require diving into the code. Once we basically agree on design, code reviews
would be easier because they'd be focused on the implementation matching the
design.
Agreed that before doing anything, we should do a design doc, and agree on
that. I think what we are discussing here is pre-design discussions.
> 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
>
> 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
