[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790451#comment-13790451
]
Nicolas Liochon commented on HBASE-5487:
----------------------------------------
bq. However, we still need someone to do various operations (servicing user
requests and other janitorial tasks).
Yeah, I agree. Balance is a good example. Less say that I'm more comfortable w/
something that lowers the role of the master than the opposite.
bq. I prefer not to use ZK
When you say this, Jimmy, do you mean "no ZK in HBase at all", or "No ZK for
permanent data", or "No ZK at all for assignment"?
bq. We should store the state in meta table which is cached in the memory.
I'm fine with that (if we can make it work :-) )
> 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)
