[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849452#comment-13849452
]
Sergey Shelukhin commented on HBASE-5487:
-----------------------------------------
IMHO this, in case of opens, promotes not being fault tolerant. In large
clusters you cannot get around servers failing and regions closing and
reopening. Snapshot should just be able to ride over that. Splits are more
interesting.
Esp. if snapshots are used more (MR over snapshots), it may be nonviable to
prevent splits and other operations for the duration of every snapshot, alter,
...
> 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
> Assignee: Sergey Shelukhin
> Priority: Critical
> Attachments: Entity management in Master - part 1.pdf, Entity
> management in Master - part 1.pdf, Is the FATE of Assignment Manager
> FATE.pdf, Region management in Master.pdf, Region management in Master5.docx,
> hbckMasterV2-long.pdf, hbckMasterV2b-long.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.4#6159)
