[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789470#comment-13789470
]
Elliott Clark commented on HBASE-5487:
--------------------------------------
bq.we still need a reliable store
HBase is a reliable store. We should be using it as such for current state.
If we co-locate the master process with meta, then the master noticing state
changes is as simples as loading a co-processor that hooks mutations. It also
means that when master wants to look up current state there's no rpc overhead.
Simply target the hregion. This allows us to reduce the number of copies of
state. No longer will we need a local hash map + what's in zk, + what's in
meta.
I think Jimmy's correct we should use zk for ephemeral only. Everything else
should be in our systems.
> 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)
