[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797368#comment-13797368
]
Sergey Shelukhin commented on HBASE-5487:
-----------------------------------------
One more update from discussion here:
- we currently have many operations that cannot be monitored other than by side
effects (create table), or at all. We need good way for user to wait for
operations. Given that we send request to master, and many operations can
recover from master failure, we cannot use simple async API with request and
async response (at least not on the lowest level - client library can hide
master failover and provide that API). The lowest-level master API should
involve some sort of persistent operation cookie, so that you could still wait
for operation after failover.
> 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: 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)
