[
https://issues.apache.org/jira/browse/HBASE-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-2341.
--------------------------
Resolution: Duplicate
The integration test suite does this. Resolving as done/duplicate
> Suite of test scripts that a.) load a cluster with a verifiable dataset and
> b.) do random kills of regionserver+datanodes in small cluster
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-2341
> URL: https://issues.apache.org/jira/browse/HBASE-2341
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Labels: moved_from_0_20_5
> Attachments: HBASE-2341-0.20.3.patch, VerifiableEditor.java,
> VerifiableEditor.java, count-slaves.rb, test.sh
>
>
> We just filed hbase-2340 but discussion up on irc has it that we need
> something more hardcore than pussy-footing inside a single jvm as hdfs-2340
> does. The point was made (tlipcon) that its hard to ensure real recovery
> working if all is in the one JVM.
> So, this issue is about scripts that can:
> + load a cluster with a dataset that we can 'verify' as in we can tell if it
> has holes in it, if data has been lost.
> + script that does random kill of a random node on some random occasion
> + Script that can check cluster for data loss
> All above should work while cluster is under load.
> The above would not sit under junit.
> This looks like a suite that we'd want to run up in ec2 using Andrew's
> scripts and our donated aws credits.
> {code}
> 16:12 < tlipcon> here's my goal: we have a 5 node cluster in the back room. I
> want to run hbase on that at near full load for a week straight while some
> process goes around screwing with it
> 16:12 < tlipcon> then I want to verify that I didn't lose a single edit over
> that week
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
