[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788415#comment-13788415
]
Devaraj Das commented on HBASE-5487:
------------------------------------
bq. We should have a single source of truth which is scalable and performs
well. I think it could be the master (in memory). All actions (including
split/merge) should be started and managed by the master.
I agree with this. We have done this in other components - HDFS, MapReduce,
Yarn, etc.... Depending on ZK for the state management brings complexity. I
think we should use ZK for only ephemeral stuff and not for storing state
there. In that regard, using ZK for discovering lost RSs is fine, but not for
storing the region states. I like the idea of the Master WAL to take care of
master crashes.
> 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 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)
