[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616885#comment-13616885
]
Enis Soztutar commented on HBASE-5487:
--------------------------------------
bq. Yeah, we could call it an "intent" log. It would have info so that a
promoted backup master can look in one place and complete an operation started
by the downed original master.
This was what I proposed in an earlier comment:
https://issues.apache.org/jira/browse/HBASE-5487?focusedCommentId=13551519&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13551519
What we need is a transactional authoritative, fault tolerant, and durable
source for ground truth about the cluster state, and execution state. Whether
we can do it using ZK or a master WAL, or a system table (using an implicit
WAL), we will have to figure it out.
> 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
> Attachments: 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 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
