[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796905#comment-13796905
]
Nicolas Liochon commented on HBASE-5487:
----------------------------------------
bq. AM and meta don't necessarily need to be collocated
If there are separated, you double the failure probability, as you need both AM
and .META. to work. Moreover, speaking to .meta. becomes a distributed problem,
while its less the case when they are collocated (only less because of HDFS).
bq. moving away from ZK for management
I believe we will need it to determine who is the AM lead. I don't really know
about storing in zookeeper vs. meta. As Jimmy said using zookeeper to do rpc
calls seems wrong however.
I guess this can be decided later. For the requirements, I don't have anything
to add to Enis' list.
> 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)
