2010-02-22 18:49:24 -05:00
<?xml version="1.0" encoding="UTF-8"?>
2010-02-24 15:17:17 -05:00
<project xmlns= "http://maven.apache.org/POM/4.0.0" xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
2011-10-23 19:03:32 -04:00
<!--
/**
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
-->
2010-02-22 18:49:24 -05:00
<modelVersion > 4.0.0</modelVersion>
2010-11-12 16:34:02 -05:00
<!-- To build a release I do this:
2012-02-11 17:12:23 -05:00
$ mvn clean site install assembly:single -Prelease
2010-11-12 16:34:02 -05:00
-->
2010-10-03 23:19:26 -04:00
<parent >
<groupId > org.apache</groupId>
<artifactId > apache</artifactId>
2010-12-21 17:32:01 -05:00
<version > 8</version>
2011-11-19 11:38:07 -05:00
<relativePath > </relativePath> <!-- no parent resolution -->
2010-10-03 23:19:26 -04:00
</parent>
2010-02-22 18:49:24 -05:00
<groupId > org.apache.hbase</groupId>
<artifactId > hbase</artifactId>
2010-05-20 01:24:32 -04:00
<packaging > jar</packaging>
2012-02-29 17:45:54 -05:00
<version > 0.95-SNAPSHOT</version>
2010-02-22 18:49:24 -05:00
<name > HBase</name>
2010-06-08 04:16:12 -04:00
<description >
2010-10-03 23:19:26 -04:00
HBase is the & lt;a href="http://hadoop.apache.org"& rt;Hadoop< /a& rt; database. Use it when you need
random, realtime read/write access to your Big Data.
2010-02-24 15:17:17 -05:00
This project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters
of commodity hardware.
</description>
2010-05-20 01:24:32 -04:00
<url > http://hbase.apache.org</url>
2010-02-24 15:17:17 -05:00
2010-02-22 18:49:24 -05:00
<scm >
2010-05-20 01:24:32 -04:00
<connection > scm:svn:http://svn.apache.org/repos/asf/hbase/trunk</connection>
<developerConnection > scm:svn:https://svn.apache.org/repos/asf/hbase/trunk</developerConnection>
<url > http://svn.apache.org/viewvc/hbase/trunk</url>
2010-02-22 18:49:24 -05:00
</scm>
2010-02-24 15:17:17 -05:00
<issueManagement >
<system > JIRA</system>
2010-10-03 23:19:26 -04:00
<url > http://issues.apache.org/jira/browse/HBASE</url>
2010-02-24 15:17:17 -05:00
</issueManagement>
<ciManagement >
<system > hudson</system>
2010-10-03 23:19:26 -04:00
<url > http://hudson.zones.apache.org/hudson/view/HBase/job/HBase-TRUNK/</url>
2010-02-24 15:17:17 -05:00
</ciManagement>
<mailingLists >
<mailingList >
<name > User List</name>
2010-05-20 01:24:32 -04:00
<subscribe > user-subscribe@hbase.apache.org</subscribe>
<unsubscribe > user-unsubscribe@hbase.apache.org</unsubscribe>
<post > user@hbase.apache.org</post>
<archive > http://mail-archives.apache.org/mod_mbox/hbase-user/</archive>
2010-02-24 15:17:17 -05:00
<otherArchives >
2011-04-05 02:24:17 -04:00
<otherArchive > http://hbase.apache.org/mail/user/</otherArchive>
2010-07-14 13:19:03 -04:00
<otherArchive > http://dir.gmane.org/gmane.comp.java.hadoop.hbase.user</otherArchive>
<otherArchive > http://search-hadoop.com/?q=& fc_project=HBase</otherArchive>
2010-02-24 15:17:17 -05:00
</otherArchives>
</mailingList>
<mailingList >
<name > Developer List</name>
2010-05-20 01:24:32 -04:00
<subscribe > dev-subscribe@hbase.apache.org</subscribe>
<unsubscribe > dev-unsubscribe@hbase.apache.org</unsubscribe>
<post > dev@hbase.apache.org</post>
<archive > http://mail-archives.apache.org/mod_mbox/hbase-dev/</archive>
2010-02-24 15:17:17 -05:00
<otherArchives >
2011-04-05 02:24:17 -04:00
<otherArchive > http://hbase.apache.org/mail/dev/</otherArchive>
2010-07-14 13:19:03 -04:00
<otherArchive > http://dir.gmane.org/gmane.comp.java.hadoop.hbase.devel</otherArchive>
<otherArchive > http://search-hadoop.com/?q=& fc_project=HBase</otherArchive>
2010-02-24 15:17:17 -05:00
</otherArchives>
</mailingList>
<mailingList >
<name > Commits List</name>
2010-05-20 01:24:32 -04:00
<subscribe > commits-subscribe@hbase.apache.org</subscribe>
<unsubscribe > commits-unsubscribe@hbase.apache.org</unsubscribe>
<archive > http://mail-archives.apache.org/mod_mbox/hbase-commits/</archive>
2011-04-05 02:24:17 -04:00
<otherArchives >
<otherArchive > http://hbase.apache.org/mail/commits/</otherArchive>
</otherArchives>
2010-02-24 15:17:17 -05:00
</mailingList>
2010-03-05 16:10:09 -05:00
<mailingList >
<name > Issues List</name>
2010-05-20 01:24:32 -04:00
<subscribe > issues-subscribe@hbase.apache.org</subscribe>
<unsubscribe > issues-unsubscribe@hbase.apache.org</unsubscribe>
<archive > http://mail-archives.apache.org/mod_mbox/hbase-issues/</archive>
2011-04-05 02:24:17 -04:00
<otherArchives >
<otherArchive > http://hbase.apache.org/mail/issues/</otherArchive>
</otherArchives>
2010-03-05 16:10:09 -05:00
</mailingList>
2010-02-24 15:17:17 -05:00
</mailingLists>
2010-02-22 18:49:24 -05:00
<developers >
<developer >
2010-02-24 15:17:17 -05:00
<id > apurtell</id>
<name > Andrew Purtell</name>
<email > apurtell@apache.org</email>
<timezone > -8</timezone>
<organization > Trend Micro</organization>
<organizationUrl > http://www.trendmicro.com</organizationUrl>
2010-12-02 19:06:57 -05:00
</developer>
2011-08-01 20:09:31 -04:00
<developer >
<id > dmeil</id>
<name > Doug Meil</name>
2011-08-06 19:58:22 -04:00
<email > dmeil@apache.org</email>
2011-08-01 20:09:31 -04:00
<timezone > -5</timezone>
<organization > Explorys</organization>
<organizationUrl > http://www.explorys.com</organizationUrl>
</developer>
2010-12-02 19:06:57 -05:00
<developer >
<id > garyh</id>
<name > Gary Helmling</name>
<email > garyh@apache.org</email>
<timezone > -8</timezone>
<organization > Trend Micro</organization>
<organizationUrl > http://www.trendmicro.com</organizationUrl>
2010-02-24 15:17:17 -05:00
</developer>
<developer >
<id > jdcryans</id>
<name > Jean-Daniel Cryans</name>
<email > jdcryans@apache.org</email>
<timezone > -8</timezone>
<organization > StumbleUpon</organization>
<organizationUrl > http://www.stumbleupon.com</organizationUrl>
</developer>
<developer >
<id > jgray</id>
<name > Jonathan Gray</name>
2011-08-01 20:09:31 -04:00
<email > jgray@fb.com</email>
2010-02-24 15:17:17 -05:00
<timezone > -8</timezone>
2010-10-03 23:19:26 -04:00
<organization > Facebook</organization>
<organizationUrl > http://www.facebook.com</organizationUrl>
2010-02-24 15:17:17 -05:00
</developer>
2012-01-19 01:29:01 -05:00
<developer >
<id > jmhsieh</id>
<name > Jonathan Hsieh</name>
<email > jmhsieh@apache.org</email>
<timezone > -8</timezone>
<organization > Cloudera</organization>
<organizationUrl > http://www.cloudera.com</organizationUrl>
</developer>
2011-10-31 16:07:12 -04:00
<developer >
<id > kannan</id>
<name > Kannan Muthukkaruppan</name>
<email > kannan@fb.com</email>
<timezone > -8</timezone>
<organization > Facebook</organization>
<organizationUrl > http://www.facebook.com</organizationUrl>
</developer>
<developer >
<id > karthik</id>
<name > Karthik Ranganathan</name>
<email > kranganathan@fb.com</email>
<timezone > -8</timezone>
<organization > Facebook</organization>
<organizationUrl > http://www.facebook.com</organizationUrl>
</developer>
2010-02-24 15:17:17 -05:00
<developer >
<id > larsgeorge</id>
<name > Lars George</name>
2010-03-04 12:54:27 -05:00
<email > larsgeorge@apache.org</email>
2010-02-24 15:17:17 -05:00
<timezone > +1</timezone>
2010-12-02 17:44:48 -05:00
<organization > Cloudera</organization>
<organizationUrl > http://www.cloudera.com/</organizationUrl>
2010-02-24 15:17:17 -05:00
</developer>
2011-10-07 22:27:08 -04:00
<developer >
<id > larsh</id>
<name > Lars Hofhansl</name>
<email > larsh@apache.org</email>
<timezone > -8</timezone>
<organization > Salesforce.com</organization>
<organizationUrl > http://www.salesforce.com/</organizationUrl>
</developer>
2012-01-25 15:35:02 -05:00
<developer >
<id > mbautin</id>
<name > Mikhail Bautin</name>
<email > mbautin@apache.org</email>
<timezone > -8</timezone>
<organization > Facebook</organization>
<organizationUrl > http://www.facebook.com</organizationUrl>
</developer>
2010-12-02 16:55:40 -05:00
<developer >
<id > nspiegelberg</id>
<name > Nicolas Spiegelberg</name>
<email > nspiegelberg@fb.com</email>
<timezone > -8</timezone>
<organization > Facebook</organization>
<organizationUrl > http://www.facebook.com</organizationUrl>
</developer>
2010-02-22 21:11:00 -05:00
<developer >
<id > rawson</id>
<name > Ryan Rawson</name>
<email > rawson@apache.org</email>
<timezone > -8</timezone>
2011-08-04 08:58:32 -04:00
<organization > CX</organization>
<organizationUrl > http://www.cx.com</organizationUrl>
2010-02-24 15:17:17 -05:00
</developer>
<developer >
<id > stack</id>
<name > Michael Stack</name>
<email > stack@apache.org</email>
<timezone > -8</timezone>
2010-04-20 17:10:44 -04:00
<organization > StumbleUpon</organization>
<organizationUrl > http://www.stumbleupon.com/</organizationUrl>
2010-02-22 21:11:00 -05:00
</developer>
2011-08-04 08:58:32 -04:00
<developer >
<id > tedyu</id>
<name > Ted Yu</name>
<email > yuzhihong@gmail.com</email>
<timezone > -8</timezone>
<organization > CarrierIQ</organization>
<organizationUrl > http://www.carrieriq.com</organizationUrl>
</developer>
2010-05-25 02:52:16 -04:00
<developer >
<id > todd</id>
<name > Todd Lipcon</name>
<email > todd@apache.org</email>
<timezone > -8</timezone>
<organization > Cloudera</organization>
<organizationUrl > http://www.cloudera.com</organizationUrl>
</developer>
2011-09-28 14:55:56 -04:00
<developer >
<id > ramkrishna</id>
<name > Ramkrishna S Vasudevan</name>
<email > ramkrishna@apache.org</email>
<timezone > +5</timezone>
<organization > Huawei</organization>
<organizationUrl > http://www.huawei.com</organizationUrl>
</developer>
2010-02-22 18:49:24 -05:00
</developers>
2010-02-24 15:17:17 -05:00
2010-02-22 18:49:24 -05:00
<repositories >
2011-03-04 20:34:24 -05:00
<repository >
<id > apache release</id>
<url > https://repository.apache.org/content/repositories/releases/</url>
</repository>
2010-11-19 19:07:12 -05:00
<repository >
2011-12-13 16:01:44 -05:00
<id > apache non-releases</id>
<name > Apache non-releases</name>
<url > http://people.apache.org/~stack/m2/repository</url>
2010-11-19 19:07:12 -05:00
<snapshots >
<enabled > false</enabled>
</snapshots>
<releases >
<enabled > true</enabled>
</releases>
</repository>
2010-02-22 18:49:24 -05:00
<repository >
<id > java.net</id>
<name > Java.Net</name>
<url > http://download.java.net/maven/2/</url>
<snapshots >
<enabled > false</enabled>
</snapshots>
<releases >
<enabled > true</enabled>
</releases>
</repository>
<repository >
<id > codehaus</id>
<name > Codehaus Public</name>
<url > http://repository.codehaus.org/</url>
<snapshots >
<enabled > false</enabled>
</snapshots>
<releases >
<enabled > true</enabled>
</releases>
</repository>
2010-12-29 00:25:26 -05:00
<repository >
<id > repository.jboss.org</id>
<url > http://repository.jboss.org/nexus/content/groups/public-jboss/</url>
<snapshots >
<enabled > false</enabled>
</snapshots>
</repository>
2011-11-19 11:38:07 -05:00
<repository >
<id > ghelmling.testing</id>
<name > Gary Helmling test repo</name>
<url > http://people.apache.org/~garyh/mvn/</url>
<snapshots >
<enabled > true</enabled>
</snapshots>
<releases >
<enabled > true</enabled>
</releases>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</repository>
2010-02-22 18:49:24 -05:00
</repositories>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2011-11-19 11:38:07 -05:00
<pluginRepositories >
<pluginRepository >
<id > ghelmling.testing</id>
<name > Gary Helmling test repo</name>
<url > http://people.apache.org/~garyh/mvn/</url>
<snapshots >
<enabled > true</enabled>
</snapshots>
<releases >
<enabled > true</enabled>
</releases>
</pluginRepository>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</pluginRepositories>
2010-02-24 15:17:17 -05:00
2010-02-22 18:49:24 -05:00
<build >
2010-02-24 15:17:17 -05:00
<!-- Some plugins (javadoc for example) can be used in the normal build - and the site phase.
These plugins inherit their options from the <reporting > section below. These settings
can be overwritten here. -->
<pluginManagement >
<plugins >
2012-03-02 12:26:34 -05:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-release-plugin</artifactId>
2012-03-06 15:25:01 -05:00
<!-- Making a release I've been using mvn 3.0 and specifying the apache - release
profile on the command line as follows:
$ ~/bin/mvn/bin/mvn -Papache-release release:perform
I've also been kiling the release:prepare step mid-way to check the
release.properties it generates at the top-level. Sometimes it refers
to HEAD rather than to the svn branch.
-->
2012-03-02 12:26:34 -05:00
<configuration >
2012-03-06 15:25:01 -05:00
<!-- You need this profile. It'll sign your artifacts.
I'm not sure if this config. actually works though.
I've been specifying -Papache-release on the command-line
-->
<releaseProfiles > apache-release</releaseProfiles>
2012-03-02 12:26:34 -05:00
<!-- This stops our running tests for each stage of maven release.
2012-03-06 15:25:01 -05:00
But it builds the test jar. From SUREFIRE-172.
2012-03-02 12:26:34 -05:00
-->
2012-03-06 15:25:01 -05:00
<arguments > -Dmaven.test.skip.exec</arguments>
2012-03-02 12:26:34 -05:00
</configuration>
</plugin>
2010-02-24 15:17:17 -05:00
<plugin >
<artifactId > maven-compiler-plugin</artifactId>
<configuration >
<source > ${compileSource}</source>
<target > ${compileSource}</target>
<showWarnings > true</showWarnings>
2010-03-22 23:56:52 -04:00
<showDeprecation > false</showDeprecation>
2010-02-24 15:17:17 -05:00
</configuration>
</plugin>
<plugin >
<artifactId > maven-surefire-plugin</artifactId>
2011-11-19 11:38:07 -05:00
<version > ${surefire.version}</version>
<dependencies >
<!-- by default surefire selects dynamically the connector to the unit tests tool.
We want to use always the same as the different connectors
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
can have different bugs and behaviour.
2011-11-19 11:38:07 -05:00
-->
<dependency >
<groupId > org.apache.maven.surefire</groupId>
2011-12-05 16:20:04 -05:00
<artifactId > ${surefire.provider}</artifactId>
2011-11-19 11:38:07 -05:00
<version > ${surefire.version}</version>
</dependency>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</dependencies>
2011-11-19 11:38:07 -05:00
2010-02-25 17:54:27 -05:00
<configuration >
2010-10-12 11:18:16 -04:00
<forkedProcessTimeoutInSeconds > 900</forkedProcessTimeoutInSeconds>
2011-11-27 18:12:52 -05:00
<argLine > -enableassertions -Xmx1900m -Djava.security.egd=file:/dev/./urandom</argLine>
2012-03-02 13:32:36 -05:00
<redirectTestOutputToFile > ${test.output.tofile}</redirectTestOutputToFile>
2010-02-25 17:54:27 -05:00
</configuration>
2010-02-24 15:17:17 -05:00
</plugin>
2011-10-03 14:33:24 -04:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-site-plugin</artifactId>
2011-10-04 11:12:39 -04:00
<version > 2.0.1</version>
2011-10-03 14:33:24 -04:00
</plugin>
2011-09-29 01:42:13 -04:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-failsafe-plugin</artifactId>
2011-11-19 11:38:07 -05:00
<version > ${surefire.version}</version>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<dependencies >
2011-12-05 16:20:04 -05:00
<dependency >
<groupId > org.apache.maven.surefire</groupId>
<artifactId > ${surefire.provider}</artifactId>
<version > ${surefire.version}</version>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</dependency>
</dependencies>
2011-09-29 01:42:13 -04:00
<configuration >
2011-12-05 16:20:04 -05:00
<includes >
<include > ${integrationtest.include}</include>
</includes>
<excludes >
<exlude > ${unittest.include}</exlude>
<exclude > **/*$*</exclude>
<exclude > ${test.exclude.pattern}</exclude>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</excludes>
2012-03-02 13:32:36 -05:00
<redirectTestOutputToFile > ${test.output.tofile}</redirectTestOutputToFile>
2011-09-29 01:42:13 -04:00
<environmentVariables >
<LD_LIBRARY_PATH > ${env.LD_LIBRARY_PATH}:${project.build.directory}/nativelib</LD_LIBRARY_PATH>
<DYLD_LIBRARY_PATH > ${env.DYLD_LIBRARY_PATH}:${project.build.directory}/nativelib</DYLD_LIBRARY_PATH>
2012-03-08 15:55:57 -05:00
<MALLOC_ARENA_MAX > 4</MALLOC_ARENA_MAX>
2011-09-29 01:42:13 -04:00
</environmentVariables>
</configuration>
<executions >
<execution >
<id > integration-test</id>
<goals >
<goal > integration-test</goal>
</goals>
</execution>
<execution >
<id > verify</id>
<goals >
<goal > verify</goal>
</goals>
</execution>
</executions>
</plugin>
2010-03-04 12:54:27 -05:00
<plugin >
<artifactId > maven-clean-plugin</artifactId>
2010-10-03 23:19:26 -04:00
<configuration >
<filesets >
<fileset >
<!-- dfs tests have build dir hardcoded. Clean it as part of
clean target-->
<directory > build</directory>
</fileset>
</filesets>
</configuration>
2010-03-04 12:54:27 -05:00
</plugin>
2011-08-03 16:53:48 -04:00
<plugin >
<artifactId > maven-surefire-report-plugin</artifactId>
2011-11-19 11:38:07 -05:00
<version > ${surefire.version}</version>
2011-08-03 16:53:48 -04:00
</plugin>
2011-09-02 19:31:37 -04:00
<plugin >
<groupId > org.apache.avro</groupId>
<artifactId > avro-maven-plugin</artifactId>
<version > ${avro.version}</version>
</plugin>
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<version > 1.5</version>
</plugin>
2012-02-03 21:59:39 -05:00
<!-- This plugin's configuration is used to store Eclipse m2e settings only. It
has no influence on the Maven build itself. m2e does not provide any safeguards against
rogue maven plugins that leak classloaders, modify random files inside workspace
or throw nasty exceptions to fail the build -->
<plugin >
<groupId > org.eclipse.m2e</groupId>
<artifactId > lifecycle-mapping</artifactId>
<version > 1.0.0</version>
<configuration >
<lifecycleMappingMetadata >
<pluginExecutions >
<pluginExecution >
<pluginExecutionFilter >
<groupId > org.apache.avro</groupId>
<artifactId > avro-maven-plugin</artifactId>
<versionRange > [1.5.3,)</versionRange>
<goals >
<goal > protocol</goal>
<goal > schema</goal>
</goals>
</pluginExecutionFilter>
<action >
<execute > </execute>
</action>
</pluginExecution>
<pluginExecution >
<pluginExecutionFilter >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-antrun-plugin</artifactId>
<versionRange > [1.3,)</versionRange>
<goals >
<goal > run</goal>
</goals>
</pluginExecutionFilter>
<action >
<execute > </execute>
</action>
</pluginExecution>
<pluginExecution >
<pluginExecutionFilter >
<groupId > org.jamon</groupId>
<artifactId > jamon-maven-plugin</artifactId>
<versionRange > [2.3.4,)</versionRange>
<goals >
<goal > translate</goal>
</goals>
</pluginExecutionFilter>
<action >
<execute > </execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
2012-02-11 17:12:23 -05:00
<plugin > <!-- in plugin management section so excludes can be inherited -->
<groupId > org.apache.rat</groupId>
<artifactId > apache-rat-plugin</artifactId>
<version > 0.8</version>
<configuration >
<excludes >
<exclude > **/.*</exclude>
2012-03-02 13:05:43 -05:00
<exclude > **/*.tgz</exclude>
2012-03-05 18:10:04 -05:00
<exclude > **/*.orig</exclude>
<exclude > **/test/**</exclude>
2012-03-02 13:05:43 -05:00
<exclude > **/8e8ab58dcf39412da19833fcd8f687ac</exclude>
2012-02-11 17:12:23 -05:00
<exclude > **/.git/**</exclude>
<exclude > **/target/**</exclude>
<exclude > **/CHANGES.txt</exclude>
<exclude > **/generated/**</exclude>
<exclude > **/conf/*</exclude>
<exclude > **/*.avpr</exclude>
<exclude > **/*.svg</exclude> <!-- vector graphics -->
<exclude > **/*.vm</exclude> <!-- apache doxia generated -->
<exclude > **/control</exclude>
<exclude > **/conffile</exclude>
<exclude > docs/*</exclude> <!-- auto - gen docs -->
<!-- It don't like freebsd license -->
<exclude > **/src/site/resources/css/freebsd_docbook.css</exclude>
</excludes>
</configuration>
</plugin>
2010-02-24 15:17:17 -05:00
</plugins>
</pluginManagement>
2010-05-20 01:24:32 -04:00
<resources >
<resource >
2010-06-10 19:21:45 -04:00
<directory > src/main/resources/</directory>
<includes >
<include > hbase-default.xml</include>
</includes>
2010-05-20 01:24:32 -04:00
</resource>
<resource >
2010-10-03 23:19:26 -04:00
<directory > ${project.build.directory}</directory>
2010-05-20 01:24:32 -04:00
<includes >
2010-10-03 23:19:26 -04:00
<include > hbase-webapps/**</include>
2010-05-20 01:24:32 -04:00
</includes>
</resource>
</resources>
2011-11-18 02:34:43 -05:00
<testResources >
<testResource >
<directory > src/test/resources</directory>
<excludes >
<exclude > hbase-site.xml</exclude>
</excludes>
</testResource>
</testResources>
2010-05-20 01:24:32 -04:00
2010-02-22 18:49:24 -05:00
<plugins >
2011-09-02 19:31:37 -04:00
<plugin >
<groupId > org.apache.avro</groupId>
<artifactId > avro-maven-plugin</artifactId>
<executions >
<execution >
<id > generate-avro-sources</id>
<phase > generate-sources</phase>
<goals >
<goal > schema</goal>
<goal > protocol</goal>
</goals>
</execution>
</executions>
<configuration >
<outputDirectory > ${project.build.directory}/generated-sources/java</outputDirectory>
</configuration>
</plugin>
2010-10-30 15:59:41 -04:00
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > xml-maven-plugin</artifactId>
2010-11-05 01:58:59 -04:00
<version > 1.0-beta-3</version>
2010-10-30 15:59:41 -04:00
<executions >
<execution >
<goals >
<goal > transform</goal>
</goals>
<phase > pre-site</phase>
</execution>
</executions>
<configuration >
<transformationSets >
<transformationSet >
<dir > ${basedir}/src/main/resources/</dir>
<includes >
<include > hbase-default.xml</include>
</includes>
<stylesheet > ${basedir}/src/main/xslt/configuration_to_docbook_section.xsl</stylesheet>
<outputDir > ${basedir}/target/site/</outputDir>
</transformationSet>
</transformationSets>
</configuration>
</plugin>
2010-07-25 17:34:46 -04:00
<plugin >
2010-10-03 23:19:26 -04:00
<groupId > com.agilejava.docbkx</groupId>
<artifactId > docbkx-maven-plugin</artifactId>
2011-12-13 16:01:44 -05:00
<version > 2.0.13</version>
2010-07-25 17:34:46 -04:00
<executions >
<execution >
2011-02-24 18:12:21 -05:00
<id > multipage</id>
<phase > pre-site</phase>
<configuration >
<xincludeSupported > true</xincludeSupported>
<navigShowtitles > true</navigShowtitles>
<chunkedOutput > true</chunkedOutput>
<useIdAsFilename > true</useIdAsFilename>
<sectionAutolabelMaxDepth > 100</sectionAutolabelMaxDepth>
<sectionAutolabel > true</sectionAutolabel>
<sectionLabelIncludesComponentLabel > true</sectionLabelIncludesComponentLabel>
<targetDirectory > ${basedir}/target/site/book/</targetDirectory>
<htmlStylesheet > ../css/freebsd_docbook.css</htmlStylesheet>
2011-12-06 01:43:54 -05:00
<htmlCustomization > src/docbkx/customization.xsl</htmlCustomization>
2011-08-10 03:07:56 -04:00
<imgSrcPath > ../images/</imgSrcPath>
2011-12-08 16:29:34 -05:00
<tocMaxDepth > 2</tocMaxDepth>
2011-12-06 01:43:54 -05:00
<insertXrefPageNumber > yes</insertXrefPageNumber>
2011-02-24 18:12:21 -05:00
</configuration>
2010-07-25 17:34:46 -04:00
<goals >
<goal > generate-html</goal>
</goals>
2011-02-24 18:12:21 -05:00
</execution>
<execution >
<id > onepage</id>
2010-07-25 17:34:46 -04:00
<phase > pre-site</phase>
2011-02-24 18:12:21 -05:00
<configuration >
<xincludeSupported > true</xincludeSupported>
<useIdAsFilename > true</useIdAsFilename>
<sectionAutolabelMaxDepth > 100</sectionAutolabelMaxDepth>
<sectionAutolabel > true</sectionAutolabel>
<sectionLabelIncludesComponentLabel > true</sectionLabelIncludesComponentLabel>
<targetDirectory > ${basedir}/target/site/</targetDirectory>
<htmlStylesheet > css/freebsd_docbook.css</htmlStylesheet>
2011-08-10 03:07:56 -04:00
<imgSrcPath > images/</imgSrcPath>
2011-12-08 16:29:34 -05:00
<tocMaxDepth > 2</tocMaxDepth>
2011-12-06 01:43:54 -05:00
<insertXrefPageNumber > yes</insertXrefPageNumber>
2011-02-24 18:12:21 -05:00
</configuration>
<goals >
<goal > generate-html</goal>
</goals>
2010-07-25 17:34:46 -04:00
</execution>
</executions>
<dependencies >
<dependency >
<groupId > org.docbook</groupId>
<artifactId > docbook-xml</artifactId>
<version > 4.4</version>
<scope > runtime</scope>
</dependency>
</dependencies>
</plugin>
2010-02-22 18:49:24 -05:00
<plugin >
<artifactId > maven-assembly-plugin</artifactId>
<configuration >
2010-02-24 15:17:17 -05:00
<tarLongFileMode > gnu</tarLongFileMode>
2010-12-07 00:25:49 -05:00
<appendAssemblyId > false</appendAssemblyId>
2010-02-22 18:49:24 -05:00
<descriptors >
2010-11-12 15:36:26 -05:00
<descriptor > src/assembly/all.xml</descriptor>
2010-02-22 18:49:24 -05:00
</descriptors>
</configuration>
2011-03-15 18:20:08 -04:00
<executions >
<execution >
<id > tarball</id>
<phase > package</phase>
<goals >
<goal > single</goal>
</goals>
</execution>
</executions>
2010-02-22 18:49:24 -05:00
</plugin>
2010-05-20 01:24:32 -04:00
<!-- Run with - Dmaven.test.skip.exec=true to build - tests.jar without running tests (this is needed for upstream projects whose tests need this jar simply for compilation) -->
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-jar-plugin</artifactId>
<executions >
<execution >
2011-03-15 18:20:08 -04:00
<phase > prepare-package</phase>
2010-05-20 01:24:32 -04:00
<goals >
<goal > test-jar</goal>
</goals>
</execution>
</executions>
<configuration >
<archive >
<manifest >
<mainClass > org/apache/hadoop/hbase/mapreduce/Driver</mainClass>
</manifest>
</archive>
<!-- Exclude these 2 packages, because their dependency _binary_ files include the sources, and Maven 2.2 appears to add them to the sources to compile, weird -->
<excludes >
<exclude > org/apache/jute/**</exclude>
<exclude > org/apache/zookeeper/**</exclude>
2010-05-20 05:02:18 -04:00
<exclude > **/*.jsp</exclude>
2011-03-02 16:00:34 -05:00
<exclude > hbase-site.xml</exclude>
<exclude > log4j.properties</exclude>
<exclude > mapred-queues.xml</exclude>
2010-05-20 01:24:32 -04:00
</excludes>
</configuration>
</plugin>
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-source-plugin</artifactId>
<executions >
<execution >
<id > attach-sources</id>
2011-03-15 18:20:08 -04:00
<phase > prepare-package</phase>
2010-05-20 01:24:32 -04:00
<goals >
<goal > jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-surefire-plugin</artifactId>
<configuration >
2011-12-05 16:20:04 -05:00
<skip > ${surefire.skipFirstPart}</skip>
2011-11-19 11:38:07 -05:00
<forkMode > ${surefire.firstPartForkMode}</forkMode>
<parallel > ${surefire.firstPartParallel}</parallel>
<perCoreThreadCount > false</perCoreThreadCount>
<threadCount > ${surefire.firstPartThreadCount}</threadCount>
2012-01-01 10:22:43 -05:00
<parallel > classes</parallel> <!-- surefire hack, if not we're using method parallelisation class ! -->
2011-11-19 11:38:07 -05:00
<groups > ${surefire.firstPartGroups}</groups>
2011-12-05 16:20:04 -05:00
<testFailureIgnore > false</testFailureIgnore>
2010-05-20 01:24:32 -04:00
</configuration>
2011-11-19 11:38:07 -05:00
<executions >
<execution >
<id > secondPartTestsExecution</id>
<phase > test</phase>
<goals > <goal > test</goal> </goals>
<configuration >
<skip > ${surefire.skipSecondPart}</skip>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<testFailureIgnore > false</testFailureIgnore>
2012-01-01 10:22:43 -05:00
<forkMode > perThread</forkMode>
<perCoreThreadCount > false</perCoreThreadCount>
<threadCount > ${surefire.secondPartThreadCount}</threadCount>
<parallel > classes</parallel> <!-- surefire hack, if not we're using method parallelisation class ! -->
2011-11-19 11:38:07 -05:00
<groups > ${surefire.secondPartGroups}</groups>
</configuration>
</execution>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</executions>
2010-05-20 01:24:32 -04:00
</plugin>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<!-- Run integration tests with mvn verify -->
2011-09-29 01:42:13 -04:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-failsafe-plugin</artifactId>
2011-11-19 11:38:07 -05:00
<configuration >
<skip > false</skip>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<forkMode > always</forkMode>
</configuration>
2011-09-29 01:42:13 -04:00
</plugin>
2010-05-20 01:24:32 -04:00
<plugin >
<artifactId > maven-antrun-plugin</artifactId>
2012-02-03 15:08:53 -05:00
<version > 1.6</version>
2010-05-20 01:24:32 -04:00
<executions >
2011-11-01 16:23:50 -04:00
<execution >
<id > arc-setup</id>
<phase > initialize</phase>
<configuration >
<tasks if= "arc" >
<get dest= "${project.build.directory}/arc-jira.tar.gz"
src="https://github.com/facebook/arc-jira/tarball/master"/>
<untar src= "${project.build.directory}/arc-jira.tar.gz" compression= "gzip"
dest="${project.build.directory}">
<patternset >
<include name= "facebook-arc-jira-*/arc_jira_lib/**" />
</patternset>
</untar>
<move todir= "${basedir}" >
<fileset dir= "${project.build.directory}" >
<include name= "facebook-arc-jira-*/arc_jira_lib/**" />
</fileset>
<mapper type= "regexp" from= "^facebook-arc-jira-([^/])*/(.*)" to= "\.\2" />
</move>
<delete includeemptydirs= "true" >
<fileset dir= "${project.build.directory}" >
<include name= "facebook-arc-jira-*" />
<include name= "arc-jira.tar.gz" />
</fileset>
</delete>
</tasks>
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
2010-05-20 01:24:32 -04:00
<execution >
2010-06-10 19:21:45 -04:00
<id > generate</id>
2010-05-20 01:24:32 -04:00
<phase > generate-sources</phase>
<configuration >
2011-09-17 14:23:31 -04:00
<target >
2010-06-10 19:21:45 -04:00
<property name= "build.webapps"
2010-10-03 23:19:26 -04:00
location="${project.build.directory}/hbase-webapps"/>
2010-06-10 19:21:45 -04:00
<property name= "src.webapps"
2010-10-03 23:19:26 -04:00
location="${basedir}/src/main/resources/hbase-webapps"/>
2010-06-10 19:21:45 -04:00
<property name= "generated.sources"
2010-10-03 23:19:26 -04:00
location="${project.build.directory}/generated-sources"/>
2010-06-10 19:21:45 -04:00
<mkdir dir= "${build.webapps}" />
<copy todir= "${build.webapps}" >
<fileset dir= "${src.webapps}" >
2010-10-03 23:19:26 -04:00
<exclude name= "**/*.jsp" />
<exclude name= "**/.*" />
<exclude name= "**/*~" />
2010-06-10 19:21:45 -04:00
</fileset>
</copy>
<!-- The compile.classpath is passed in by maven -->
2010-05-20 01:24:32 -04:00
<taskdef classname= "org.apache.jasper.JspC" name= "jspcompiler" classpathref= "maven.compile.classpath" />
2010-06-10 19:21:45 -04:00
<mkdir dir= "${build.webapps}/master/WEB-INF" />
<jspcompiler uriroot= "${src.webapps}/master"
2011-09-02 19:31:37 -04:00
outputdir="${generated.sources}/java"
2010-10-03 23:19:26 -04:00
package="org.apache.hadoop.hbase.generated.master"
webxml="${build.webapps}/master/WEB-INF/web.xml"/>
2010-06-10 19:21:45 -04:00
<mkdir dir= "${build.webapps}/regionserver/WEB-INF" />
<jspcompiler uriroot= "${src.webapps}/regionserver"
2011-09-02 19:31:37 -04:00
outputdir="${generated.sources}/java"
2010-10-03 23:19:26 -04:00
package="org.apache.hadoop.hbase.generated.regionserver"
webxml="${build.webapps}/regionserver/WEB-INF/web.xml"/>
2010-06-10 19:21:45 -04:00
2010-10-27 19:22:59 -04:00
<exec executable= "sh" >
2011-09-02 19:31:37 -04:00
<arg line= "${basedir}/src/saveVersion.sh ${project.version} ${generated.sources}/java" />
2010-10-27 19:22:59 -04:00
</exec>
2011-09-17 14:23:31 -04:00
</target>
2010-05-20 01:24:32 -04:00
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
2011-02-09 14:12:08 -05:00
<execution >
<phase > process-resources</phase>
<configuration >
2011-09-17 14:23:31 -04:00
<target >
2011-02-09 14:12:08 -05:00
<replace file= "${project.build.outputDirectory}/hbase-default.xml"
token="@@@VERSION@@@" value="${project.version}" />
2011-06-06 19:16:09 -04:00
<mkdir dir= "${project.build.directory}/nativelib" />
<exec executable= "tar" dir= "${project.build.directory}/nativelib" failonerror= "false" >
<arg value= "xf" />
<arg value= "hadoop-snappy-nativelibs.tar" />
</exec>
2011-09-17 14:23:31 -04:00
</target>
2011-02-09 14:12:08 -05:00
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
2011-06-06 19:16:09 -04:00
<execution >
<id > package</id>
<phase > package</phase>
<configuration >
<target >
<!-- Complements the assembly -->
2011-11-18 02:34:43 -05:00
<mkdir dir= "${project.build.directory}/${project.build.finalName}/${project.build.finalName}/lib/native/${build.platform}" />
2011-06-06 19:16:09 -04:00
<!-- Using Unix cp to preserve symlinks, using script to handle wildcards -->
<echo file= "${project.build.directory}/copynativelibs.sh" >
if [ `ls ${project.build.directory}/nativelib | wc -l` -ne 0 ]; then
2011-11-18 02:34:43 -05:00
cp -PR ${project.build.directory}/nativelib/lib* ${project.build.directory}/${project.build.finalName}/${project.build.finalName}/lib/native/${build.platform}
2011-06-06 19:16:09 -04:00
fi
</echo>
<exec executable= "sh" dir= "${project.build.directory}" failonerror= "true" >
<arg line= "./copynativelibs.sh" />
</exec>
<!-- Using Unix tar to preserve symlinks -->
<exec executable= "tar" failonerror= "yes"
2011-12-12 15:37:21 -05:00
dir="${project.build.directory}/${project.build.finalName}">
2011-06-06 19:16:09 -04:00
<arg value= "czf" />
2011-11-18 02:34:43 -05:00
<arg value= "${project.build.directory}/${project.build.finalName}.tar.gz" />
2011-12-12 15:37:21 -05:00
<arg value= "${project.build.finalName}/" />
2011-06-06 19:16:09 -04:00
</exec>
</target>
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
2010-05-20 01:24:32 -04:00
</executions>
</plugin>
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
2012-02-03 15:08:53 -05:00
<version > 1.5</version>
2010-05-20 01:24:32 -04:00
<executions >
<execution >
2011-09-02 19:31:37 -04:00
<id > jspcSource-packageInfo-Avro-source</id>
2010-05-20 01:24:32 -04:00
<phase > generate-sources</phase>
<goals >
<goal > add-source</goal>
</goals>
<configuration >
<sources >
2011-09-07 02:30:56 -04:00
<source > ${project.build.directory}/generated-jamon</source>
2011-09-02 19:31:37 -04:00
<source > ${project.build.directory}/generated-sources/java</source>
2010-05-20 01:24:32 -04:00
</sources>
</configuration>
</execution>
</executions>
</plugin>
2011-05-03 15:07:00 -04:00
<plugin >
<groupId > org.jamon</groupId>
<artifactId > jamon-maven-plugin</artifactId>
<version > 2.3.4</version>
<executions >
<execution >
<phase > generate-sources</phase>
<goals >
<goal > translate</goal>
</goals>
<configuration >
<templateSourceDir > src/main/jamon</templateSourceDir>
<templateOutputDir > target/generated-jamon</templateOutputDir>
</configuration>
</execution>
</executions>
</plugin>
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-eclipse-plugin</artifactId>
2011-09-17 14:23:31 -04:00
<version > 2.8</version>
2011-05-03 15:07:00 -04:00
<configuration >
<additionalProjectnatures >
<projectnature > org.jamon.project.jamonnature</projectnature>
</additionalProjectnatures>
<buildcommands >
<buildcommand > org.jamon.project.templateBuilder</buildcommand>
<buildcommand > org.eclipse.jdt.core.javabuilder</buildcommand>
<buildcommand > org.jamon.project.markerUpdater</buildcommand>
</buildcommands>
<additionalConfig >
<file >
<name > .settings/org.jamon.prefs</name>
<content > # now
eclipse.preferences.version=1
templateSourceDir=src/main/jamon
templateOutputDir=target/generated-jamon
</content>
</file>
</additionalConfig>
</configuration>
</plugin>
2012-03-28 11:33:28 -04:00
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > findbugs-maven-plugin</artifactId>
<configuration >
<findbugsXmlOutput > true</findbugsXmlOutput>
<xmlOutput > true</xmlOutput>
<excludeFilterFile > ${basedir}/dev-support/findbugs-exclude.xml</excludeFilterFile>
<effort > Max</effort>
</configuration>
</plugin>
2010-02-22 18:49:24 -05:00
</plugins>
</build>
2010-02-24 15:17:17 -05:00
2010-04-20 17:10:44 -04:00
<properties >
2011-12-06 01:43:54 -05:00
<maven.build.timestamp.format >
yyyy-MM-dd'T'HH:mm
</maven.build.timestamp.format>
<buildDate >
${maven.build.timestamp}
</buildDate>
2010-04-20 17:10:44 -04:00
<compileSource > 1.6</compileSource>
2010-10-03 23:19:26 -04:00
<!-- Dependencies -->
2011-09-02 19:31:37 -04:00
<avro.version > 1.5.3</avro.version>
2010-04-20 17:10:44 -04:00
<commons-cli.version > 1.2</commons-cli.version>
2010-10-03 23:19:26 -04:00
<commons-codec.version > 1.4</commons-codec.version>
<commons-httpclient.version > 3.1</commons-httpclient.version> <!-- pretty outdated -->
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<commons-io.version > 2.1</commons-io.version>
2010-05-20 01:24:32 -04:00
<commons-lang.version > 2.5</commons-lang.version>
2010-10-03 23:19:26 -04:00
<commons-logging.version > 1.1.1</commons-logging.version>
2010-05-20 01:24:32 -04:00
<commons-math.version > 2.1</commons-math.version>
2011-12-13 16:01:44 -05:00
<commons-configuration.version > 1.6</commons-configuration.version>
2011-04-18 14:12:04 -04:00
<guava.version > r09</guava.version>
2011-08-20 16:27:09 -04:00
<jackson.version > 1.5.5</jackson.version>
2010-05-20 01:24:32 -04:00
<jasper.version > 5.5.23</jasper.version>
<jaxb-api.version > 2.1</jaxb-api.version>
2010-12-20 03:51:45 -05:00
<jetty.version > 6.1.26</jetty.version>
2010-10-03 23:19:26 -04:00
<jetty.jspapi.version > 6.1.14</jetty.jspapi.version>
<jersey.version > 1.4</jersey.version>
2011-12-13 16:01:44 -05:00
<jruby.version > 1.6.5</jruby.version>
2011-11-19 11:38:07 -05:00
<junit.version > 4.10-HBASE-1</junit.version>
2010-10-03 23:19:26 -04:00
<log4j.version > 1.2.16</log4j.version>
<mockito-all.version > 1.8.5</mockito-all.version>
2011-08-23 18:34:23 -04:00
<protobuf.version > 2.4.0a</protobuf.version>
2010-10-03 23:19:26 -04:00
<slf4j.version > 1.5.8</slf4j.version> <!-- newer version available -->
<stax-api.version > 1.0.1</stax-api.version>
2012-01-17 12:38:58 -05:00
<thrift.version > 0.8.0</thrift.version>
2012-02-17 15:58:56 -05:00
<zookeeper.version > 3.4.3</zookeeper.version>
2011-06-07 16:53:25 -04:00
<hadoop-snappy.version > 0.0.1-SNAPSHOT</hadoop-snappy.version>
2011-03-14 21:10:27 -04:00
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<package.prefix > /usr</package.prefix>
<package.conf.dir > /etc/hbase</package.conf.dir>
2011-03-15 18:20:08 -04:00
<package.log.dir > /var/log/hbase</package.log.dir>
<package.pid.dir > /var/run/hbase</package.pid.dir>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<package.release > 1</package.release>
2011-03-15 18:20:08 -04:00
<!-- also must update this when we bump version -->
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<package.version > 0.91.0</package.version>
2011-09-17 14:23:31 -04:00
<final.name > ${project.artifactId}-${project.version}</final.name>
2011-12-05 16:20:04 -05:00
<!-- Test inclusion patterns used by failsafe configuration -->
<unittest.include > **/Test*.java</unittest.include>
<integrationtest.include > **/IntegrationTest*.java</integrationtest.include>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2012-01-01 10:22:43 -05:00
<surefire.version > 2.12-TRUNK-HBASE-2</surefire.version>
2011-12-05 16:20:04 -05:00
<surefire.provider > surefire-junit47</surefire.provider>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2012-01-01 10:22:43 -05:00
<!-- default: run small & medium, medium with 2 threads -->
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.skipFirstPart > false</surefire.skipFirstPart>
2011-12-05 16:20:04 -05:00
<surefire.skipSecondPart > false</surefire.skipSecondPart>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2011-12-05 16:20:04 -05:00
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
2012-01-01 10:22:43 -05:00
<surefire.firstPartParallel > classes</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
2012-01-01 10:22:43 -05:00
<surefire.secondPartThreadCount > 2</surefire.secondPartThreadCount>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartGroups > org.apache.hadoop.hbase.SmallTests</surefire.firstPartGroups>
2011-12-05 16:20:04 -05:00
<surefire.secondPartGroups > org.apache.hadoop.hbase.MediumTests</surefire.secondPartGroups>
2012-03-02 13:32:36 -05:00
<test.output.tofile > true</test.output.tofile>
2010-04-20 17:10:44 -04:00
</properties>
2010-10-03 23:19:26 -04:00
<!-- Sorted by groups of dependencies then groupId and artifactId -->
<dependencies >
<!--
Note: There are a few exclusions to prevent duplicate code in different jars to be included:
* org.mortbay.jetty:servlet-api, javax.servlet:servlet-api: These are excluded because they are
the same implementations. I chose org.mortbay.jetty:servlet-api-2.5 instead, which is a third
implementation of the same, because Hadoop also uses this version
* javax.servlet:jsp-api in favour of org.mortbay.jetty:jsp-api-2.1
* javax.xml.stream:stax-api in favour of stax:stax-api
-->
2010-04-20 17:10:44 -04:00
2011-12-05 16:20:04 -05:00
2010-10-03 23:19:26 -04:00
<!-- General dependencies -->
<dependency >
<groupId > com.google.guava</groupId>
<artifactId > guava</artifactId>
<version > ${guava.version}</version>
</dependency>
2010-05-20 01:24:32 -04:00
<dependency >
<groupId > commons-cli</groupId>
<artifactId > commons-cli</artifactId>
2010-10-03 23:19:26 -04:00
<version > ${commons-cli.version}</version>
</dependency>
2011-12-13 16:01:44 -05:00
<dependency >
<groupId > commons-configuration</groupId>
<artifactId > commons-configuration</artifactId>
<version > ${commons-configuration.version}</version>
</dependency>
2011-03-14 19:38:57 -04:00
<dependency >
<groupId > com.github.stephenc.high-scale-lib</groupId>
<artifactId > high-scale-lib</artifactId>
<version > 1.1.1</version>
</dependency>
2010-10-03 23:19:26 -04:00
<dependency >
<groupId > commons-codec</groupId>
<artifactId > commons-codec</artifactId>
<version > ${commons-codec.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > commons-httpclient</groupId>
<artifactId > commons-httpclient</artifactId>
<version > ${commons-httpclient.version}</version>
</dependency>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<dependency >
<groupId > commons-io</groupId>
<artifactId > commons-io</artifactId>
<version > ${commons-io.version}</version>
</dependency>
2010-05-20 01:24:32 -04:00
<dependency >
<groupId > commons-lang</groupId>
<artifactId > commons-lang</artifactId>
<version > ${commons-lang.version}</version>
</dependency>
<dependency >
<groupId > commons-logging</groupId>
<artifactId > commons-logging</artifactId>
2010-10-03 23:19:26 -04:00
<version > ${commons-logging.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > log4j</groupId>
<artifactId > log4j</artifactId>
2010-10-03 23:19:26 -04:00
<version > ${log4j.version}</version>
</dependency>
<dependency >
2010-12-29 00:25:26 -05:00
<groupId > org.apache.avro</groupId>
2010-10-03 23:19:26 -04:00
<artifactId > avro</artifactId>
<version > ${avro.version}</version>
2011-03-03 17:13:51 -05:00
<exclusions >
<exclusion >
<groupId > com.thoughtworks.paranamer</groupId>
<artifactId > paranamer</artifactId>
</exclusion>
<exclusion >
<groupId > com.thoughtworks.paranamer</groupId>
<artifactId > paranamer-ant</artifactId>
</exclusion>
</exclusions>
2010-10-03 23:19:26 -04:00
</dependency>
2011-09-02 19:31:37 -04:00
<dependency >
<groupId > org.apache.avro</groupId>
<artifactId > avro-ipc</artifactId>
<version > ${avro.version}</version>
</dependency>
2010-10-03 23:19:26 -04:00
<dependency >
2010-11-12 14:36:57 -05:00
<groupId > org.apache.zookeeper</groupId>
2010-10-03 23:19:26 -04:00
<artifactId > zookeeper</artifactId>
<version > ${zookeeper.version}</version>
2011-03-03 17:13:51 -05:00
<exclusions >
<exclusion >
<groupId > jline</groupId>
<artifactId > jline</artifactId>
</exclusion>
</exclusions>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
2011-04-26 18:40:25 -04:00
<groupId > org.apache.thrift</groupId>
2011-03-04 20:34:24 -05:00
<artifactId > libthrift</artifactId>
2010-05-20 01:24:32 -04:00
<version > ${thrift.version}</version>
<exclusions >
<exclusion >
<groupId > org.slf4j</groupId>
<artifactId > slf4j-simple</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency >
2010-10-03 23:19:26 -04:00
<groupId > org.jruby</groupId>
<artifactId > jruby-complete</artifactId>
<version > ${jruby.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > org.mortbay.jetty</groupId>
<artifactId > jetty</artifactId>
<version > ${jetty.version}</version>
2010-10-03 23:19:26 -04:00
<exclusions >
<exclusion >
<groupId > org.mortbay.jetty</groupId>
<artifactId > servlet-api</artifactId>
</exclusion>
</exclusions>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > org.mortbay.jetty</groupId>
<artifactId > jetty-util</artifactId>
<version > ${jetty.version}</version>
</dependency>
<dependency >
<groupId > org.mortbay.jetty</groupId>
2010-10-03 23:19:26 -04:00
<artifactId > jsp-2.1</artifactId>
<version > ${jetty.jspapi.version}</version>
2011-03-03 17:13:51 -05:00
<exclusions >
<exclusion >
<groupId > ant</groupId>
<artifactId > ant</artifactId>
</exclusion>
</exclusions>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > org.mortbay.jetty</groupId>
2010-10-03 23:19:26 -04:00
<artifactId > jsp-api-2.1</artifactId>
2010-06-01 00:01:06 -04:00
<version > ${jetty.jspapi.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
<dependency >
<groupId > org.mortbay.jetty</groupId>
2010-10-03 23:19:26 -04:00
<artifactId > servlet-api-2.5</artifactId>
2010-06-01 00:01:06 -04:00
<version > ${jetty.jspapi.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<!-- While jackson is also a dependency of both jersey and avro, these
can bring in jars from different, incompatible versions. We force
2011-08-20 16:27:09 -04:00
the same version with these dependencies -->
<dependency >
<groupId > org.codehaus.jackson</groupId>
<artifactId > jackson-core-asl</artifactId>
<version > ${jackson.version}</version>
</dependency>
<dependency >
<groupId > org.codehaus.jackson</groupId>
<artifactId > jackson-mapper-asl</artifactId>
<version > ${jackson.version}</version>
</dependency>
<dependency >
<groupId > org.codehaus.jackson</groupId>
<artifactId > jackson-jaxrs</artifactId>
<version > ${jackson.version}</version>
</dependency>
<dependency >
<groupId > org.codehaus.jackson</groupId>
<artifactId > jackson-xc</artifactId>
<version > ${jackson.version}</version>
</dependency>
2010-05-20 01:24:32 -04:00
<dependency >
2010-10-03 23:19:26 -04:00
<groupId > org.slf4j</groupId>
<artifactId > slf4j-api</artifactId>
<version > ${slf4j.version}</version>
</dependency>
<dependency >
<groupId > org.slf4j</groupId>
<artifactId > slf4j-log4j12</artifactId>
<version > ${slf4j.version}</version>
2010-05-20 01:24:32 -04:00
</dependency>
2010-05-20 05:02:18 -04:00
<dependency >
<!-- If this is not in the runtime lib, we get odd
"2009-02-27 11:38:39.504::WARN: failed jsp
java.lang.NoSuchFieldError: IS_SECURITY_ENABLED"
exceptions out of jetty deploying webapps.
St.Ack Thu May 20 01:04:41 PDT 2010
-->
<groupId > tomcat</groupId>
<artifactId > jasper-compiler</artifactId>
<version > ${jasper.version}</version>
2010-10-03 23:19:26 -04:00
<scope > runtime</scope>
<exclusions >
<exclusion >
<groupId > javax.servlet</groupId>
<artifactId > jsp-api</artifactId>
</exclusion>
<exclusion >
<groupId > javax.servlet</groupId>
<artifactId > servlet-api</artifactId>
</exclusion>
2011-03-03 17:13:51 -05:00
<exclusion >
<groupId > ant</groupId>
<artifactId > ant</artifactId>
</exclusion>
2010-10-03 23:19:26 -04:00
</exclusions>
2010-05-20 05:02:18 -04:00
</dependency>
2010-05-20 01:24:32 -04:00
<dependency >
2010-10-03 23:19:26 -04:00
<groupId > tomcat</groupId>
<artifactId > jasper-runtime</artifactId>
<version > ${jasper.version}</version>
<scope > runtime</scope>
<exclusions >
<exclusion >
<groupId > javax.servlet</groupId>
<artifactId > servlet-api</artifactId>
</exclusion>
</exclusions>
2010-05-20 01:24:32 -04:00
</dependency>
2011-05-03 15:07:00 -04:00
<dependency >
<groupId > org.jamon</groupId>
<artifactId > jamon-runtime</artifactId>
<version > 2.3.1</version>
</dependency>
2010-05-20 01:24:32 -04:00
<!-- REST dependencies -->
<dependency >
<groupId > com.google.protobuf</groupId>
<artifactId > protobuf-java</artifactId>
<version > ${protobuf.version}</version>
</dependency>
<dependency >
<groupId > com.sun.jersey</groupId>
<artifactId > jersey-core</artifactId>
<version > ${jersey.version}</version>
</dependency>
<dependency >
<groupId > com.sun.jersey</groupId>
<artifactId > jersey-json</artifactId>
<version > ${jersey.version}</version>
</dependency>
<dependency >
<groupId > com.sun.jersey</groupId>
<artifactId > jersey-server</artifactId>
<version > ${jersey.version}</version>
</dependency>
<dependency >
2010-10-03 23:19:26 -04:00
<groupId > javax.xml.bind</groupId>
<artifactId > jaxb-api</artifactId>
<version > ${jaxb-api.version}</version>
<exclusions >
<exclusion >
<groupId > javax.xml.stream</groupId>
<artifactId > stax-api</artifactId>
</exclusion>
</exclusions>
2010-06-13 02:53:50 -04:00
</dependency>
<dependency >
2010-10-03 23:19:26 -04:00
<groupId > stax</groupId>
<artifactId > stax-api</artifactId>
<version > ${stax-api.version}</version>
2010-06-13 02:53:50 -04:00
</dependency>
2010-05-20 01:24:32 -04:00
<!-- Test dependencies -->
<dependency >
<groupId > junit</groupId>
<artifactId > junit</artifactId>
2010-10-03 23:19:26 -04:00
<version > ${junit.version}</version>
<scope > test</scope>
2010-05-20 01:24:32 -04:00
</dependency>
2010-06-01 20:40:48 -04:00
<dependency >
<groupId > org.mockito</groupId>
<artifactId > mockito-all</artifactId>
2010-10-03 23:19:26 -04:00
<version > ${mockito-all.version}</version>
<scope > test</scope>
2010-06-01 20:40:48 -04:00
</dependency>
2010-05-20 01:24:32 -04:00
<dependency >
<groupId > org.apache.commons</groupId>
<artifactId > commons-math</artifactId>
<version > ${commons-math.version}</version>
<scope > test</scope>
</dependency>
</dependencies>
2010-04-20 17:10:44 -04:00
2010-04-12 19:50:51 -04:00
<!--
To publish, use the following settings.xml file ( placed in ~/.m2/settings.xml )
2010-02-24 15:17:17 -05:00
2010-04-12 19:50:51 -04:00
<settings >
<servers >
<server >
<id > apache.releases.https</id>
<username > hbase_committer</username>
<password > ********</password>
</server>
<server >
<id > apache.snapshots.https</id>
<username > hbase_committer</username>
<password > ********</password>
</server>
</servers>
</settings>
$ mvn deploy
(or)
2010-06-07 19:06:24 -04:00
$ mvn -s /my/path/settings.xml deploy
2010-04-12 19:50:51 -04:00
-->
2011-03-15 18:20:08 -04:00
<profiles >
<profile >
<id > rpm</id>
<build >
<plugins >
<plugin >
<artifactId > maven-antrun-plugin</artifactId>
<version > 1.6</version>
<executions >
<execution >
<id > build-rpm</id>
<phase > package</phase>
<configuration >
<target >
<ant antfile= "${basedir}/src/packages/build.xml" >
<target name= "package-rpm" />
<target name= "package-conf-pseudo-rpm" />
</ant>
</target>
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
</executions>
</plugin>
2012-02-17 20:07:13 -05:00
<plugin >
<artifactId > maven-javadoc-plugin</artifactId>
<version > 2.6.1</version>
<configuration >
<docfilessubdirs > true</docfilessubdirs>
</configuration>
<executions >
<execution >
<phase > prepare-package</phase>
<goals >
<goal > javadoc</goal>
</goals>
</execution>
</executions>
</plugin>
2011-03-15 18:20:08 -04:00
</plugins>
</build>
</profile>
<profile >
<id > deb</id>
<build >
<plugins >
<plugin >
<artifactId > maven-antrun-plugin</artifactId>
<version > 1.6</version>
<executions >
<execution >
<id > build-deb</id>
<phase > package</phase>
<configuration >
<target >
2011-04-26 18:40:25 -04:00
<property name= "artifactId" value= "${project.artifactId}" />
2011-03-15 18:20:08 -04:00
<ant antfile= "${basedir}/src/packages/build.xml" >
<target name= "package-deb" />
<target name= "package-conf-pseudo-deb" />
</ant>
</target>
</configuration>
<goals >
<goal > run</goal>
</goals>
</execution>
</executions>
<dependencies >
<dependency >
<groupId > org.vafer</groupId>
<artifactId > jdeb</artifactId>
<version > 0.8</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
</profile>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2011-06-06 19:16:09 -04:00
<profile >
<id > os.linux</id>
<activation >
<activeByDefault > false</activeByDefault>
<os >
<family > Linux</family>
</os>
</activation>
<properties >
<build.platform > ${os.name}-${os.arch}-${sun.arch.data.model}</build.platform>
</properties>
</profile>
<profile >
<id > os.mac</id>
<activation >
<os >
<family > Mac</family>
</os>
</activation>
<properties >
<build.platform > Mac_OS_X-${sun.arch.data.model}</build.platform>
</properties>
</profile>
2012-02-11 17:12:23 -05:00
<!-- this profile should be activated for release builds -->
<profile >
<id > release</id>
<build >
<plugins >
<plugin >
<groupId > org.apache.rat</groupId>
<artifactId > apache-rat-plugin</artifactId>
<executions >
<execution >
<phase > package</phase>
<goals >
<goal > check</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
2011-06-06 19:16:09 -04:00
<profile >
<id > hadoop-snappy</id>
<activation >
<activeByDefault > false</activeByDefault>
<property >
<name > snappy</name>
</property>
</activation>
<dependencies >
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-snappy</artifactId>
<version > ${hadoop-snappy.version}</version>
</dependency>
</dependencies>
<build >
<plugins >
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-dependency-plugin</artifactId>
<executions >
<execution >
<id > get-hadoop-snappy-native</id>
<phase > generate-resources</phase>
<goals >
<goal > copy</goal>
</goals>
<configuration >
<artifactItems >
<artifactItem >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-snappy</artifactId>
<version > ${hadoop-snappy.version}</version>
<classifier > ${build.platform}</classifier>
<type > tar</type>
<overWrite > false</overWrite>
<outputDirectory > ${project.build.directory}/nativelib</outputDirectory>
<destFileName > hadoop-snappy-nativelibs.tar</destFileName>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
2011-08-23 18:47:53 -04:00
2011-12-13 16:01:44 -05:00
<!-- profile for building against Hadoop 1.0.x: This is the default. -->
2011-08-23 18:47:53 -04:00
<profile >
2011-12-13 16:01:44 -05:00
<id > hadoop-1.0</id>
2011-08-23 18:47:53 -04:00
<activation >
<property >
2011-09-07 02:17:05 -04:00
<name > !hadoop.profile</name>
2011-08-23 18:47:53 -04:00
</property>
</activation>
<properties >
2012-04-05 13:30:57 -04:00
<hadoop.version > 1.0.2</hadoop.version>
2011-08-23 18:47:53 -04:00
</properties>
<dependencies >
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-core</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-08-23 18:47:53 -04:00
<exclusions >
<exclusion >
<groupId > hsqldb</groupId>
<artifactId > hsqldb</artifactId>
</exclusion>
<exclusion >
<groupId > net.sf.kosmosfs</groupId>
<artifactId > kfs</artifactId>
</exclusion>
<exclusion >
<groupId > org.eclipse.jdt</groupId>
<artifactId > core</artifactId>
</exclusion>
<exclusion >
<groupId > net.java.dev.jets3t</groupId>
<artifactId > jets3t</artifactId>
</exclusion>
<exclusion >
<groupId > oro</groupId>
<artifactId > oro</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-test</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-08-23 18:47:53 -04:00
<scope > test</scope>
</dependency>
</dependencies>
2011-11-18 02:34:43 -05:00
<build >
<plugins >
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<executions >
<execution >
<id > add-test-resource</id>
<goals >
<goal > add-test-resource</goal>
</goals>
<configuration >
<resources >
<resource >
<directory > src/test/resources</directory>
<includes >
<include > hbase-site.xml</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
2011-08-23 18:47:53 -04:00
</profile>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2011-11-18 02:34:43 -05:00
<!-- profile for building against Hadoop 0.20+security -->
<profile >
<id > security</id>
2011-11-20 14:46:21 -05:00
<properties >
2012-04-05 13:30:57 -04:00
<hadoop.version > 1.0.2</hadoop.version>
2011-11-20 14:46:21 -05:00
</properties>
2011-11-18 02:34:43 -05:00
<build >
2011-11-19 11:38:07 -05:00
<finalName > ${project.artifactId}-${project.version}-security</finalName>
2011-11-18 02:34:43 -05:00
<plugins >
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<executions >
<execution >
<id > add-source</id>
<goals >
<goal > add-source</goal>
</goals>
<configuration >
<sources >
<source > ${project.basedir}/security/src/main/java</source>
</sources>
</configuration>
</execution>
<execution >
<id > add-test-source</id>
<goals >
<goal > add-test-source</goal>
</goals>
<configuration >
<sources >
<source > ${project.basedir}/security/src/test/java</source>
</sources>
</configuration>
</execution>
<execution >
<id > add-test-resource</id>
<goals >
<goal > add-test-resource</goal>
</goals>
<configuration >
<resources >
<resource >
<directory > ${project.basedir}/security/src/test/resources</directory>
<includes >
<include > hbase-site.xml</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
2011-09-07 02:17:05 -04:00
<!--
profile for building against Hadoop 0.22.0. Activate using:
mvn -Dhadoop.profile=22
-->
<profile >
<id > hadoop-0.22</id>
<activation >
<property >
<name > hadoop.profile</name>
<value > 22</value>
</property>
</activation>
<properties >
2011-12-16 19:13:28 -05:00
<hadoop.version > 0.22.0</hadoop.version>
2011-09-07 02:17:05 -04:00
</properties>
<dependencies >
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-common</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<exclusions >
<!-- Needs more work, tightening -->
<exclusion >
<groupId > hsqldb</groupId>
<artifactId > hsqldb</artifactId>
</exclusion>
<exclusion >
<groupId > net.sf.kosmosfs</groupId>
<artifactId > kfs</artifactId>
</exclusion>
<exclusion >
<groupId > org.eclipse.jdt</groupId>
<artifactId > core</artifactId>
</exclusion>
<exclusion >
<groupId > net.java.dev.jets3t</groupId>
<artifactId > jets3t</artifactId>
</exclusion>
<exclusion >
<groupId > oro</groupId>
<artifactId > oro</artifactId>
</exclusion>
<exclusion >
<groupId > jdiff</groupId>
<artifactId > jdiff</artifactId>
</exclusion>
<exclusion >
<groupId > org.apache.lucene</groupId>
<artifactId > lucene-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-hdfs</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<exclusions >
<!-- Needs more work, tightening -->
<exclusion >
<groupId > hsqldb</groupId>
<artifactId > hsqldb</artifactId>
</exclusion>
<exclusion >
<groupId > net.sf.kosmosfs</groupId>
<artifactId > kfs</artifactId>
</exclusion>
<exclusion >
<groupId > org.eclipse.jdt</groupId>
<artifactId > core</artifactId>
</exclusion>
<exclusion >
<groupId > net.java.dev.jets3t</groupId>
<artifactId > jets3t</artifactId>
</exclusion>
<exclusion >
<groupId > oro</groupId>
<artifactId > oro</artifactId>
</exclusion>
<exclusion >
<groupId > jdiff</groupId>
<artifactId > jdiff</artifactId>
</exclusion>
<exclusion >
<groupId > org.apache.lucene</groupId>
<artifactId > lucene-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-mapred</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<exclusions >
<!-- Needs more work, tightening -->
<exclusion >
<groupId > hsqldb</groupId>
<artifactId > hsqldb</artifactId>
</exclusion>
<exclusion >
<groupId > net.sf.kosmosfs</groupId>
<artifactId > kfs</artifactId>
</exclusion>
<exclusion >
<groupId > org.eclipse.jdt</groupId>
<artifactId > core</artifactId>
</exclusion>
<exclusion >
<groupId > net.java.dev.jets3t</groupId>
<artifactId > jets3t</artifactId>
</exclusion>
<exclusion >
<groupId > oro</groupId>
<artifactId > oro</artifactId>
</exclusion>
<exclusion >
<groupId > jdiff</groupId>
<artifactId > jdiff</artifactId>
</exclusion>
<exclusion >
<groupId > org.apache.lucene</groupId>
<artifactId > lucene-core</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- test deps for hadoop - 0.22 profile -->
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-common-test</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<scope > test</scope>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-hdfs-test</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<scope > test</scope>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-mapred-test</artifactId>
<version > ${hadoop.version}</version>
2011-11-23 00:56:40 -05:00
<optional > true</optional>
2011-09-07 02:17:05 -04:00
<scope > test</scope>
</dependency>
</dependencies>
2011-11-18 02:34:43 -05:00
<build >
<plugins >
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<executions >
<execution >
<id > add-test-resource</id>
<goals >
<goal > add-test-resource</goal>
</goals>
<configuration >
<resources >
<resource >
<directory > src/test/resources</directory>
<includes >
<include > hbase-site.xml</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
2011-09-07 02:17:05 -04:00
</profile>
2011-08-23 18:47:53 -04:00
<!--
profile for building against Hadoop 0.23.0. Activate using:
2011-09-07 02:17:05 -04:00
mvn -Dhadoop.profile=23
2011-08-23 18:47:53 -04:00
-->
<profile >
<id > hadoop-0.23</id>
<activation >
<property >
2011-09-07 02:17:05 -04:00
<name > hadoop.profile</name>
<value > 23</value>
2011-08-23 18:47:53 -04:00
</property>
</activation>
<properties >
2012-03-06 12:38:22 -05:00
<hadoop.version > 0.23.2-SNAPSHOT</hadoop.version>
2011-08-23 18:47:53 -04:00
</properties>
<dependencies >
<dependency >
<groupId > org.apache.hadoop</groupId>
2012-02-17 15:21:52 -05:00
<artifactId > hadoop-client</artifactId>
2011-08-23 18:47:53 -04:00
<version > ${hadoop.version}</version>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-annotations</artifactId>
<version > ${hadoop.version}</version>
</dependency>
<!-- test deps for hadoop - 0.23 profile -->
<dependency >
<groupId > org.apache.hadoop</groupId>
2012-02-17 15:21:52 -05:00
<artifactId > hadoop-minicluster</artifactId>
2011-08-23 18:47:53 -04:00
<version > ${hadoop.version}</version>
2012-02-17 15:21:52 -05:00
<scope > compile</scope>
2011-11-29 01:04:17 -05:00
</dependency>
2011-08-23 18:47:53 -04:00
</dependencies>
2011-11-18 02:34:43 -05:00
<build >
<plugins >
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<executions >
<execution >
<id > add-test-resource</id>
<goals >
<goal > add-test-resource</goal>
</goals>
<configuration >
<resources >
<resource >
<directory > src/test/resources</directory>
<includes >
<include > hbase-site.xml</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
2012-02-23 20:07:03 -05:00
<plugin >
<artifactId > maven-dependency-plugin</artifactId>
<executions >
<execution >
<id > create-mrapp-generated-classpath</id>
<phase > generate-test-resources</phase>
<goals >
<goal > build-classpath</goal>
</goals>
<configuration >
<!-- needed to run the unit test for DS to generate
the required classpath that is required in the env
of the launch container in the mini mr/yarn cluster
-->
<outputFile > ${project.build.directory}/test-classes/mrapp-generated-classpath</outputFile>
</configuration>
</execution>
</executions>
</plugin>
2011-11-18 02:34:43 -05:00
</plugins>
</build>
2011-08-23 18:47:53 -04:00
</profile>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2012-03-08 12:58:08 -05:00
<!--
profile for building against Hadoop 0.24.0. Activate using:
mvn -Dhadoop.profile=24
-->
<profile >
<id > hadoop-0.24</id>
<activation >
<property >
<name > hadoop.profile</name>
<value > 24</value>
</property>
</activation>
<properties >
<hadoop.version > 0.24.0-SNAPSHOT</hadoop.version>
</properties>
<dependencies >
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-common</artifactId>
<version > ${hadoop.version}</version>
</dependency>
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-annotations</artifactId>
<version > ${hadoop.version}</version>
</dependency>
<!-- test deps for hadoop - 0.24 profile -->
<dependency >
<groupId > org.apache.hadoop</groupId>
<artifactId > hadoop-minicluster</artifactId>
<version > ${hadoop.version}</version>
<scope > compile</scope>
</dependency>
</dependencies>
<build >
<plugins >
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > build-helper-maven-plugin</artifactId>
<executions >
<execution >
<id > add-test-resource</id>
<goals >
<goal > add-test-resource</goal>
</goals>
<configuration >
<resources >
<resource >
<directory > src/test/resources</directory>
<includes >
<include > hbase-site.xml</include>
</includes>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
<plugin >
<artifactId > maven-dependency-plugin</artifactId>
<executions >
<execution >
<id > create-mrapp-generated-classpath</id>
<phase > generate-test-resources</phase>
<goals >
<goal > build-classpath</goal>
</goals>
<configuration >
<!-- needed to run the unit test for DS to generate
the required classpath that is required in the env
of the launch container in the mini mr/yarn cluster
-->
<outputFile > ${project.build.directory}/test-classes/mrapp-generated-classpath</outputFile>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<!-- profiles for the tests
2011-11-19 11:38:07 -05:00
See as well the properties of the project for the values
when no profile is active. -->
<profile > <!-- Use it to launch the tests without parallelisation -->
<id > nonParallelTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > always</surefire.firstPartForkMode>
<surefire.firstPartParallel > none</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
2011-11-19 11:38:07 -05:00
</properties>
</profile>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<profile > <!-- Use it to launch the tests in parallel in the same JVM -->
2011-11-19 11:38:07 -05:00
<id > parallelTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
<surefire.firstPartParallel > classes</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
2011-11-19 11:38:07 -05:00
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
<profile > <!-- Use it to launch the tests in the same JVM -->
2011-11-19 11:38:07 -05:00
<id > singleJVMTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
<surefire.firstPartParallel > none</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
<surefire.skipFirstPart > false</surefire.skipFirstPart>
<surefire.skipSecondPart > true</surefire.skipSecondPart>
<surefire.firstPartGroups > </surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-11-19 11:38:07 -05:00
<profile > <!-- Use it to launch small tests only -->
<id > runSmallTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
<surefire.firstPartParallel > none</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
<surefire.skipFirstPart > false</surefire.skipFirstPart>
<surefire.skipSecondPart > true</surefire.skipSecondPart>
<surefire.firstPartGroups > org.apache.hadoop.hbase.SmallTests</surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
<surefire.secondPartGroups > </surefire.secondPartGroups>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-11-19 11:38:07 -05:00
<profile > <!-- Use it to launch medium tests only -->
<id > runMediumTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
2011-12-05 16:20:04 -05:00
<surefire.firstPartForkMode > always</surefire.firstPartForkMode>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.skipFirstPart > false</surefire.skipFirstPart>
<surefire.skipSecondPart > true</surefire.skipSecondPart>
<surefire.firstPartGroups > org.apache.hadoop.hbase.MediumTests</surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
<surefire.secondPartGroups > </surefire.secondPartGroups>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-11-19 11:38:07 -05:00
<profile > <!-- Use it to launch large tests only -->
<id > runLargeTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
2011-12-05 16:20:04 -05:00
<surefire.firstPartForkMode > always</surefire.firstPartForkMode>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.skipFirstPart > false</surefire.skipFirstPart>
<surefire.skipSecondPart > true</surefire.skipSecondPart>
<surefire.firstPartGroups > org.apache.hadoop.hbase.LargeTests</surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
<surefire.secondPartGroups > </surefire.secondPartGroups>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-11-19 11:38:07 -05:00
<profile > <!-- Use it to launch small & medium tests -->
<id > runDevTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
<surefire.firstPartParallel > none</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
<surefire.skipFirstPart > false</surefire.skipFirstPart>
<surefire.skipSecondPart > false</surefire.skipSecondPart>
<surefire.firstPartGroups > org.apache.hadoop.hbase.SmallTests</surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
<surefire.secondPartGroups > org.apache.hadoop.hbase.MediumTests</surefire.secondPartGroups>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-11-19 11:38:07 -05:00
<profile > <!-- Use it to launch all tests -->
<id > runAllTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
<surefire.firstPartForkMode > once</surefire.firstPartForkMode>
<surefire.firstPartParallel > none</surefire.firstPartParallel>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartThreadCount > 1</surefire.firstPartThreadCount>
2012-01-01 23:22:34 -05:00
<surefire.secondPartThreadCount > 4</surefire.secondPartThreadCount>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.skipFirstPart > false</surefire.skipFirstPart>
2011-11-19 11:38:07 -05:00
<surefire.skipSecondPart > false</surefire.skipSecondPart>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartGroups > org.apache.hadoop.hbase.SmallTests</surefire.firstPartGroups>
2011-11-19 11:38:07 -05:00
<surefire.secondPartGroups > org.apache.hadoop.hbase.MediumTests,org.apache.hadoop.hbase.LargeTests</surefire.secondPartGroups>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-12-05 16:20:04 -05:00
<profile > <!-- Use it skip the surefire tests but no the failsafe tests -->
<id > skipSurefireTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<properties >
<surefire.skipFirstPart > true</surefire.skipFirstPart>
2011-12-05 16:20:04 -05:00
<surefire.skipSecondPart > true</surefire.skipSecondPart>
</properties>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
</profile>
2011-12-05 16:20:04 -05:00
<profile > <!-- Use it to launch tests locally -->
<id > localTests</id>
<activation >
<activeByDefault > false</activeByDefault>
</activation>
<properties >
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.provider > surefire-junit4</surefire.provider>
<surefire.version > 2.10</surefire.version>
<surefire.firstPartForkMode > always</surefire.firstPartForkMode>
<surefire.skipFirstPart > false</surefire.skipFirstPart>
2011-12-05 16:20:04 -05:00
<surefire.skipSecondPart > true</surefire.skipSecondPart>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
<surefire.firstPartGroups > </surefire.firstPartGroups>
2011-12-05 16:20:04 -05:00
</properties>
</profile>
2011-03-15 18:20:08 -04:00
</profiles>
[jira] [HBASE-4908] HBase cluster test tool (port from 0.89-fb)
Summary:
Porting one of our HBase cluster test tools (a single-process multi-threaded
load generator and verifier) from 0.89-fb to trunk.
I cleaned up the code a bit compared to what's in 0.89-fb, and discovered that
it has some features that I have not tried yet (some kind of a kill test, and
some way to run HBase as multiple processes on one machine).
The main utility of this piece of code for us has been the HBaseClusterTest
command-line tool (called HBaseTest in 0.89-fb), which we usually invoke as a
load test in our five-node dev cluster testing, e.g.:
hbase org.apache.hadoop.hbase.util.LoadTestTool -write 50:100:20 -tn loadtest4
-read 100:10 -zk <zk_quorum_node> -bloom ROWCOL -compression LZO -key_window 5
-max_read_errors 10000 -num_keys 10000000000 -start_key 0
Test Plan:
Run this on a dev cluster. Run all unit tests.
Reviewers: stack, Karthik, Kannan, nspiegelberg, JIRA
Reviewed By: nspiegelberg
CC: stack, nspiegelberg, mbautin, Karthik
Differential Revision: 549
git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1211746 13f79535-47bb-0310-9956-ffa450edef68
2011-12-07 21:38:27 -05:00
2010-02-24 15:17:17 -05:00
<!-- See http://jira.codehaus.org/browse/MSITE - 443 why the settings need to be here and not in pluginManagement. -->
2010-02-22 18:49:24 -05:00
<reporting >
<plugins >
2010-03-04 12:54:27 -05:00
<plugin >
<artifactId > maven-project-info-reports-plugin</artifactId>
<version > 2.1.2</version>
2010-07-14 18:02:57 -04:00
<reportSets >
<reportSet >
<reports >
<report > project-team</report>
<report > mailing-list</report>
<report > cim</report>
<report > issue-tracking</report>
<report > license</report>
<report > scm</report>
<report > index</report>
</reports>
</reportSet>
</reportSets>
2010-03-04 12:54:27 -05:00
</plugin>
2010-02-22 18:49:24 -05:00
<plugin >
<artifactId > maven-site-plugin</artifactId>
2011-10-04 11:12:39 -04:00
<version > 2.0.1</version>
2010-02-22 18:49:24 -05:00
<configuration >
<inputEncoding > UTF-8</inputEncoding>
<outputEncoding > UTF-8</outputEncoding>
2010-07-28 13:33:53 -04:00
<templateFile > src/site/site.vm</templateFile>
2010-02-22 18:49:24 -05:00
</configuration>
</plugin>
<plugin >
<artifactId > maven-javadoc-plugin</artifactId>
2010-02-24 15:17:17 -05:00
<version > 2.6.1</version>
2010-02-22 18:49:24 -05:00
<configuration >
2010-02-24 15:17:17 -05:00
<docfilessubdirs > true</docfilessubdirs>
2010-02-22 18:49:24 -05:00
</configuration>
2010-07-14 18:02:57 -04:00
<reportSets >
<reportSet >
<id > default</id>
<reports >
<report > javadoc</report>
</reports>
</reportSet>
</reportSets>
2010-02-24 15:17:17 -05:00
<!--
This is probably not needed, given the smallness of the HBase source code, but left here in case
<minmemory > 128m</minmemory>
<maxmemory > 1024m</maxmemory>
-->
2010-02-22 18:49:24 -05:00
</plugin>
2010-05-15 17:06:11 -04:00
<!-- Disabled for now.
2010-02-22 18:49:24 -05:00
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > cobertura-maven-plugin</artifactId>
2010-03-04 12:54:27 -05:00
<version > 2.3</version>
2010-02-22 18:49:24 -05:00
</plugin>
2010-05-15 17:06:11 -04:00
-->
2010-02-22 18:49:24 -05:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-jxr-plugin</artifactId>
2010-03-04 12:54:27 -05:00
<version > 2.1</version>
2010-02-22 18:49:24 -05:00
</plugin>
2010-05-15 17:06:11 -04:00
<!-- Disabled for now
2010-02-22 18:49:24 -05:00
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > jdepend-maven-plugin</artifactId>
2010-03-04 12:54:27 -05:00
<version > 2.0-beta-2</version>
2010-02-22 18:49:24 -05:00
</plugin>
<plugin >
<artifactId > maven-changes-plugin</artifactId>
2010-03-04 12:54:27 -05:00
<version > 2.3</version>
2010-02-22 18:49:24 -05:00
<configuration >
<issueLinkTemplate > %URL%/browse/%ISSUE%</issueLinkTemplate>
</configuration>
<reportSets >
<reportSet >
<reports >
<report > changes-report</report>
</reports>
</reportSet>
</reportSets>
</plugin>
2010-03-04 12:54:27 -05:00
<plugin >
<groupId > com.atlassian.maven.plugins</groupId>
<artifactId > maven-clover2-plugin</artifactId>
<version > 2.6.3</version>
</plugin>
<plugin >
<groupId > org.codehaus.mojo</groupId>
<artifactId > taglist-maven-plugin</artifactId>
<version > 2.4</version>
</plugin>
2010-05-15 17:06:11 -04:00
<plugin >
<artifactId > maven-surefire-report-plugin</artifactId>
<version > 2.5</version>
</plugin>
2010-03-04 12:54:27 -05:00
<plugin >
<artifactId > maven-dependency-plugin</artifactId>
<version > 2.1</version>
</plugin>
2010-06-08 04:16:12 -04:00
-->
2010-05-15 17:06:11 -04:00
<plugin >
<groupId > org.apache.rat</groupId>
<artifactId > apache-rat-plugin</artifactId>
2012-02-11 17:12:23 -05:00
<version > 0.8</version>
2010-05-15 17:06:11 -04:00
</plugin>
2011-09-29 01:42:13 -04:00
<plugin >
<groupId > org.apache.maven.plugins</groupId>
<artifactId > maven-surefire-report-plugin</artifactId>
2011-10-04 11:12:39 -04:00
<version > 2.7.2</version>
2011-09-29 01:42:13 -04:00
<reportSets >
<reportSet >
<id > integration-tests</id>
<reports >
<report > report-only</report>
</reports>
<configuration >
<outputName > failsafe-report</outputName>
<reportsDirectories >
<reportsDirectory > ${project.build.directory}/failsafe-reports</reportsDirectory>
</reportsDirectories>
</configuration>
</reportSet>
</reportSets>
</plugin>
2010-02-22 18:49:24 -05:00
</plugins>
</reporting>
</project>