[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797472#comment-13797472
]
Sergey Shelukhin commented on HBASE-5487:
-----------------------------------------
Ok, I split the doc in half. That way it will be easier to read and manager.
Part 1 is ready (as a current version), and describes high level design,
operation semantics and interaction (I think the latter might be interesting
for [~jmhsieh]
It also tries to capture the requirement lists above and high-level
implementation (whatever is agreed upon to some degree).
Please tell me if something is missing or wrong.
Part 2 I will keep attaching updates. It covers the design of operations -
state machines, exact steps, how client tracks it, how recovery works, etc. It
will follow part 1.
> 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: Sergey Shelukhin
> Priority: Critical
> Attachments: Entity management in Master - part 1.pdf, Region
> management in Master5.docx, Region management in Master.pdf
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
