[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796982#comment-13796982
]
ramkrishna.s.vasudevan commented on HBASE-5487:
-----------------------------------------------
Started going through this document. With my experience with AM definitely the
number of states we have and the dependency on ZK callback makes things bit
difficult to understand and track and the state of truth is spread across.
In the doc, for the create table scenario there are cases where the Create
table failure on master abort will result in a table creation that has lesser
number of regions actually specified by the clients in the split.
The master failover part is another critical area as how we collect the alive
and dead RS list and the list of Regions that were partially in either
opening/closing and splitting. It is this failiure condition where we end up in
lot of hidden areas.
Will read the document and share the ideas if any.
> 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
> 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)
