[
https://issues.apache.org/jira/browse/HBASE-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250769#comment-13250769
]
Keith Turner commented on HBASE-5487:
-------------------------------------
Accumulo 1.3 cannot not survive running our random walk test w/ the agitator (a
perl script that kills accumulo processes, it not as devious as Todd's
gremlins).
Random walk + Agitation + Accumulo 1.3 == foobar
Attempting the above would leave Accumulo in an inconsistent state (like
corrupted metadata table) or test clients would die with unexpected exceptions.
My point is that while developing FATE it was nice to have Random Walk +
Agitation to really beat up the FATE framework and the FATE table operations.
We also wrote some new random walk test for 1.4 that were even meaner.
> 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
> Labels: noob
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
