[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849738#comment-13849738
]
Andrew Purtell commented on HBASE-5487:
---------------------------------------
bq. Snapshots can still be secured
This is debatable, and that is my point for bringing it up here. All of the
enterprise customers I interact with universally want more than table-level
granularity, which is why we spent so much time on cell granularity features
recently - all of which are totally defeated by MR over snapshots.
Bringing up MR snapshots as technical justification for other arguments needs
qualification that MR over snapshots itself may have limited applicability.
> 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)
