[accumulo-website] branch asf-site updated: Jekyll build from master:598e53c
This is an automated email from the ASF dual-hosted git repository. mmiller pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/accumulo-website.git The following commit(s) were added to refs/heads/asf-site by this push: new 9eea79e Jekyll build from master:598e53c 9eea79e is described below commit 9eea79ed1d0507cc543dbab2c46cfbf1ae21cd93 Author: Mike Miller AuthorDate: Thu Apr 4 18:12:48 2019 -0400 Jekyll build from master:598e53c Update 1.9.3 release notes (#165) Co-authored-by: Ed Coleman --- feed.xml | 4 +- release/accumulo-1.9.3/index.html | 200 -- search_data.json | 2 +- 3 files changed, 109 insertions(+), 97 deletions(-) diff --git a/feed.xml b/feed.xml index 60bf5d5..2546279 100644 --- a/feed.xml +++ b/feed.xml @@ -6,8 +6,8 @@ https://accumulo.apache.org/ https://accumulo.apache.org/feed.xml; rel="self" type="application/rss+xml"/> -Thu, 04 Apr 2019 13:12:05 -0400 -Thu, 04 Apr 2019 13:12:05 -0400 +Thu, 04 Apr 2019 18:12:41 -0400 +Thu, 04 Apr 2019 18:12:41 -0400 Jekyll v3.7.3 diff --git a/release/accumulo-1.9.3/index.html b/release/accumulo-1.9.3/index.html index 8c928ce..db6967f 100644 --- a/release/accumulo-1.9.3/index.html +++ b/release/accumulo-1.9.3/index.html @@ -166,27 +166,67 @@ step instructions for running example code Multiple Fixes for Write Ahead Logs -Fixes issues where a reference may be created in zookeeper and referenced in the metadata table or -a large number of empty wal files are created, which can slow recovery. +This release fixes a number of issues with Write Ahead Logs that slow or prevent recovery +and in some cases lead to data loss. The fixes reduce the number of WALS that need to be +referenced by a tserver, improve error handing of WAL issues, and improve WAL clean up processes. -Fix improper handling of new WAL failure https://github.com/apache/accumulo/issues/1005;>#949 https://github.com/apache/accumulo/issues/1057;>#1057 Fixes issues where a wal that -does not exist (create failed or was deleted by a tserver) but the reference was created in -zookeeper. The reference to the non-existent wal causes metadata operations to hang until reference -is removed. + + +Eliminates a race condition that could result in data loss during recovery. +In cases where the GC deletes unreferenced WAL files as the master is simultaneously +attempting to create the list of WALs necessary for recovery, the master will skip +files that should be used in the recovery, resulting in data loss. Fixed in https://github.com/apache/accumulo/issues/866;>#866. + + +If the metadata table has references to a non-existent WAL file, operations +for that table will hang. This occurs when files published to zookeeper have existing +references but subsequent failures have occurred in the WAL files, or if a tserver +removes the file. Reported in https://github.com/apache/accumulo/issues/949;>#949 and fixed in https://github.com/apache/accumulo/issues/1057;>#1005. + + +tserver failures could result in the creation of many files that are unreferenced and +never written to, resulting in files with a header but no data. Recovery tries to +handle these as “empty” files which slows the recovery process. This was fixed in https://github.com/apache/accumulo/issues/845;>#823. + + +When the number of WALs referenced by a tserver exceeds a threshold, the tserver will +flush and minor compact the oldest log to limit the number of wal references needed by +that tserver. This reduces the number of WALs referenced by many tservers and speeds +recovery by reducing the number of WALs needed during recovery. Addressed by https://github.com/apache/accumulo/issues/860;>#854. + + +During tablet recovery, filter out logs that do not define the tablet. https://github.com/apache/accumulo/issues/881;>#881 + + +If a tserver fails sorting, a marker file is written to the recovery directory. +The presence of this marker prevents any subsequent attempts at recovery from succeeding. +Fixed by modifying the WAL RecoveryLogReader to handle failed file markers in https://github.com/apache/accumulo/issues/1048;>#961. + + +Use UnsynchronizedBuffer for optimized writeV methods (writeVLong abd writeVInt) +in Mutations so that only one write call is necessary to the underlying outputstream. +This was mainly done as an attempt to improve WAL performance. It “should” help +performance of mutations overall since the Hadoop WriteableUtils method can make +multiple write calls per long. https://github.com/apache/accumulo/issues/669;>#669 + + -Fix Unreferenced closed WALs that were never written to https://github.com/apache/accumulo/issues/845;>#823 Fixes issue where failures -could result in the creation of many files with a header
[accumulo-website] branch master updated: Update 1.9.3 release notes (#165)
This is an automated email from the ASF dual-hosted git repository. mmiller pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/accumulo-website.git The following commit(s) were added to refs/heads/master by this push: new 598e53c Update 1.9.3 release notes (#165) 598e53c is described below commit 598e53c39e4ea724e8fc12b928d27a9309c9152c Author: Mike Miller AuthorDate: Thu Apr 4 18:08:18 2019 -0400 Update 1.9.3 release notes (#165) Co-authored-by: Ed Coleman --- _posts/release/2018-07-18-accumulo-1.9.3.md | 182 ++-- 1 file changed, 88 insertions(+), 94 deletions(-) diff --git a/_posts/release/2018-07-18-accumulo-1.9.3.md b/_posts/release/2018-07-18-accumulo-1.9.3.md index ceeda36..9f12d39 100644 --- a/_posts/release/2018-07-18-accumulo-1.9.3.md +++ b/_posts/release/2018-07-18-accumulo-1.9.3.md @@ -16,27 +16,52 @@ Users of any previous version of 1.8 or 1.9 are encouraged to upgrade ### Multiple Fixes for Write Ahead Logs -Fixes issues where a reference may be created in zookeeper and referenced in the metadata table or -a large number of empty wal files are created, which can slow recovery. +This release fixes a number of issues with Write Ahead Logs that slow or prevent recovery +and in some cases lead to data loss. The fixes reduce the number of WALS that need to be +referenced by a tserver, improve error handing of WAL issues, and improve WAL clean up processes. -Fix improper handling of new WAL failure [#949] [#1005] [#1057] Fixes issues where a wal that -does not exist (create failed or was deleted by a tserver) but the reference was created in -zookeeper. The reference to the non-existent wal causes metadata operations to hang until reference -is removed. ++ Eliminates a race condition that could result in data loss during recovery. +In cases where the GC deletes unreferenced WAL files as the master is simultaneously +attempting to create the list of WALs necessary for recovery, the master will skip +files that should be used in the recovery, resulting in data loss. Fixed in [#866]. -Fix Unreferenced closed WALs that were never written to [#823] [#845] Fixes issue where failures -could result in the creation of many files with a header and no data. Recovery treated these -as an "empty" files during recovery. ++ If the metadata table has references to a non-existent WAL file, operations +for that table will hang. This occurs when files published to zookeeper have existing +references but subsequent failures have occurred in the WAL files, or if a tserver +removes the file. Reported in [#949] and fixed in [#1005] [#1057]. -Handle many tablets referencing many WALs [#854] [#860] Reduces the number of wals that a tserver -references, this speeds recovery by reducing the number of wals needed during recovery. When a the -number of wals referenced by a tserver exceeds a threshold, the tserver will flush and minor -compactthe oldest log to limit the number of wal references. ++ tserver failures could result in the creation of many files that are unreferenced and +never written to, resulting in files with a header but no data. Recovery tries to +handle these as "empty" files which slows the recovery process. This was fixed in [#823] [#845]. -Fix WAL RecoveryLogReader error on failed file [#961] [#1048] If a tserver fails sorting, a marker -file is written to the recovery directory. The presence of this marker prevented any subsequent -attempts at recovery from succeeding. -(originally [ACCUMULO-4861](https://issues.apache.org/jira/browse/ACCUMULO-4861) ++ When the number of WALs referenced by a tserver exceeds a threshold, the tserver will +flush and minor compact the oldest log to limit the number of wal references needed by +that tserver. This reduces the number of WALs referenced by many tservers and speeds +recovery by reducing the number of WALs needed during recovery. Addressed by [#854] [#860]. + ++ During tablet recovery, filter out logs that do not define the tablet. [#881] + ++ If a tserver fails sorting, a marker file is written to the recovery directory. +The presence of this marker prevents any subsequent attempts at recovery from succeeding. +Fixed by modifying the WAL RecoveryLogReader to handle failed file markers in [#961] [#1048]. + ++ Use UnsynchronizedBuffer for optimized writeV methods (writeVLong abd writeVInt) +in Mutations so that only one write call is necessary to the underlying outputstream. +This was mainly done as an attempt to improve WAL performance. It "should" help +performance of mutations overall since the Hadoop WriteableUtils method can make +multiple write calls per long. [#669] + +Moved optimized writeVLong and writeVInt to UnsynchronizedBuffer +to replace use of WriteableUtils methods. Each optimized method will +only make one write call to the underlying outputstream. + +### Multiple Fixes for
[accumulo] branch master updated: Update jetty to latest (CVE-2018-12545)
This is an automated email from the ASF dual-hosted git repository. ctubbsii pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/accumulo.git The following commit(s) were added to refs/heads/master by this push: new f707758 Update jetty to latest (CVE-2018-12545) f707758 is described below commit f7077580e2ffe5f5a9ea1a248f5417b780bc71fb Author: Christopher Tubbs AuthorDate: Thu Apr 4 16:28:44 2019 -0400 Update jetty to latest (CVE-2018-12545) --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 4e90b90..1a59378 100644 --- a/pom.xml +++ b/pom.xml @@ -132,7 +132,7 @@ 2.2.4 2.3.0 2.27 -9.4.11.v20180605 +9.4.15.v20190215 1.8 1.8
[accumulo] branch master updated (1bc7833 -> e6b1b11)
This is an automated email from the ASF dual-hosted git repository. ctubbsii pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/accumulo.git. from 1bc7833 Move similar tests into PermissionsIT add 382c0a5 Upgrade jetty to latest 9.2 version (#1072) new e6b1b11 Merge branch '1.9' The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes:
[accumulo] 01/01: Merge branch '1.9'
This is an automated email from the ASF dual-hosted git repository. ctubbsii pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/accumulo.git commit e6b1b11fd88d0be07c86483c3d3148c3605e52ed Merge: 1bc7833 382c0a5 Author: Christopher Tubbs AuthorDate: Thu Apr 4 15:52:20 2019 -0400 Merge branch '1.9'
[accumulo] branch 1.9 updated: Upgrade jetty to latest 9.2 version (#1072)
This is an automated email from the ASF dual-hosted git repository. ctubbsii pushed a commit to branch 1.9 in repository https://gitbox.apache.org/repos/asf/accumulo.git The following commit(s) were added to refs/heads/1.9 by this push: new 382c0a5 Upgrade jetty to latest 9.2 version (#1072) 382c0a5 is described below commit 382c0a5b461720bc5e2ca1b29d5c22cd740b7b92 Author: Mike Miller AuthorDate: Thu Apr 4 15:45:42 2019 -0400 Upgrade jetty to latest 9.2 version (#1072) --- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index bbf0d10..09a0e30 100644 --- a/pom.xml +++ b/pom.xml @@ -132,7 +132,7 @@ 3.1.0-incubating false -9.2.17.v20160517 +9.2.26.v20180806 1.7 1.7 3.0.5
[accumulo] branch master updated (33317e8 -> 1bc7833)
This is an automated email from the ASF dual-hosted git repository. mmiller pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/accumulo.git. from 33317e8 Update MAC javadoc new 9292f71 Move test into PermissionsIT new c46163d PR update new 1bc7833 Move similar tests into PermissionsIT The 9926 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../accumulo/test/ArbitraryTablePropertiesIT.java | 229 - .../accumulo/test/functional/PermissionsIT.java| 58 +- 2 files changed, 55 insertions(+), 232 deletions(-) delete mode 100644 test/src/main/java/org/apache/accumulo/test/ArbitraryTablePropertiesIT.java
[accumulo-website] branch asf-site updated: Jekyll build from master:0d03060
This is an automated email from the ASF dual-hosted git repository. mmiller pushed a commit to branch asf-site in repository https://gitbox.apache.org/repos/asf/accumulo-website.git The following commit(s) were added to refs/heads/asf-site by this push: new a20cc39 Jekyll build from master:0d03060 a20cc39 is described below commit a20cc395d627cba9a49b6320e88110bf23aacee7 Author: Mike Miller AuthorDate: Thu Apr 4 13:12:12 2019 -0400 Jekyll build from master:0d03060 Update release notes for 1.9.3 WIP (#164) * Update release notes for 1.9.3 * Updates from Keith, Ed and Christopher --- feed.xml | 4 +- release/accumulo-1.9.3/index.html | 147 +- search_data.json | 2 +- 3 files changed, 147 insertions(+), 6 deletions(-) diff --git a/feed.xml b/feed.xml index 59ae16c..60bf5d5 100644 --- a/feed.xml +++ b/feed.xml @@ -6,8 +6,8 @@ https://accumulo.apache.org/ https://accumulo.apache.org/feed.xml; rel="self" type="application/rss+xml"/> -Fri, 22 Mar 2019 14:02:53 -0400 -Fri, 22 Mar 2019 14:02:53 -0400 +Thu, 04 Apr 2019 13:12:05 -0400 +Thu, 04 Apr 2019 13:12:05 -0400 Jekyll v3.7.3 diff --git a/release/accumulo-1.9.3/index.html b/release/accumulo-1.9.3/index.html index e85e9b4..8c928ce 100644 --- a/release/accumulo-1.9.3/index.html +++ b/release/accumulo-1.9.3/index.html @@ -164,6 +164,30 @@ step instructions for running example code Notable Changes +Multiple Fixes for Write Ahead Logs + +Fixes issues where a reference may be created in zookeeper and referenced in the metadata table or +a large number of empty wal files are created, which can slow recovery. + +Fix improper handling of new WAL failure https://github.com/apache/accumulo/issues/1005;>#949 https://github.com/apache/accumulo/issues/1057;>#1057 Fixes issues where a wal that +does not exist (create failed or was deleted by a tserver) but the reference was created in +zookeeper. The reference to the non-existent wal causes metadata operations to hang until reference +is removed. + +Fix Unreferenced closed WALs that were never written to https://github.com/apache/accumulo/issues/845;>#823 Fixes issue where failures +could result in the creation of many files with a header and no data. Recovery treated these +as an “empty” files during recovery. + +Handle many tablets referencing many WALs https://github.com/apache/accumulo/issues/860;>#854 Reduces the number of wals that a tserver +references, this speeds recovery by reducing the number of wals needed during recovery. When a the +number of wals referenced by a tserver exceeds a threshold, the tserver will flush and minor +compactthe oldest log to limit the number of wal references. + +Fix WAL RecoveryLogReader error on failed file https://github.com/apache/accumulo/issues/1048;>#961 If a tserver fails sorting, a marker +file is written to the recovery directory. The presence of this marker prevented any subsequent +attempts at recovery from succeeding. +(originally https://issues.apache.org/jira/browse/ACCUMULO-4861;>ACCUMULO-4861 + Fix ArrayOutOfBounds error when new files are created (affects all previous versions) Accumulo maintains a 1-up counter to keep file names and other identifiers @@ -186,17 +210,134 @@ I0123abc.rf, you are probably at low risk from this bug. This issue was fixed in pull request https://github.com/apache/accumulo/issues/562;>#562 -~Another notable item here~ (affects ~versions~) +Stop locking during compaction + +Compactions were acquiring the tablet lock between each key value. +This created unnecessary contention with other operations like scan and +bulk imports. For https://github.com/apache/accumulo/issues/1031;>#1031 the the synchronization was removed +by https://github.com/apache/accumulo/issues/1032;>#1032 . + +Fixed splitting tablets with files and no data + +The split code assumed that if a tablet had files that it had data in +those files. There are some edge case where this is not true. Updated +the split code to handle this https://github.com/apache/accumulo/issues/998;>#998 https://github.com/apache/accumulo/issues/999;>#999 . + +Log when a scan waits a long time for files. + +Accumulo has a configurable limit on the max number of files open in a +tserver for all scans. When too many files are open, scans must wait. +In https://github.com/apache/accumulo/issues/978;>#978 and https://github.com/apache/accumulo/issues/981;>#981 scans that wait too long for files +now log a message. + +Fixed race condition in table existance check. + +The Accumulo client code that checks if tables exists had a race +condition. The race was fixed in https://github.com/apache/accumulo/issues/768;>#768 and https://github.com/apache/accumulo/issues/973;>#973 -More description here. This was fixed in [#NUM]. +Support running Mini Accumulo using Java 11 -Other
[accumulo-website] branch master updated: Update release notes for 1.9.3 WIP (#164)
This is an automated email from the ASF dual-hosted git repository.
mmiller pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/master by this push:
new 0d03060 Update release notes for 1.9.3 WIP (#164)
0d03060 is described below
commit 0d0306048aae45cbbef33e670a2371249c6e0665
Author: Mike Miller
AuthorDate: Thu Apr 4 13:09:27 2019 -0400
Update release notes for 1.9.3 WIP (#164)
* Update release notes for 1.9.3
* Updates from Keith, Ed and Christopher
---
_posts/release/2018-07-18-accumulo-1.9.3.md | 210 +++-
1 file changed, 207 insertions(+), 3 deletions(-)
diff --git a/_posts/release/2018-07-18-accumulo-1.9.3.md
b/_posts/release/2018-07-18-accumulo-1.9.3.md
index f24c5ad..ceeda36 100644
--- a/_posts/release/2018-07-18-accumulo-1.9.3.md
+++ b/_posts/release/2018-07-18-accumulo-1.9.3.md
@@ -14,6 +14,30 @@ Users of any previous version of 1.8 or 1.9 are encouraged
to upgrade
## Notable Changes
+### Multiple Fixes for Write Ahead Logs
+
+Fixes issues where a reference may be created in zookeeper and referenced in
the metadata table or
+a large number of empty wal files are created, which can slow recovery.
+
+Fix improper handling of new WAL failure [#949] [#1005] [#1057] Fixes issues
where a wal that
+does not exist (create failed or was deleted by a tserver) but the reference
was created in
+zookeeper. The reference to the non-existent wal causes metadata operations to
hang until reference
+is removed.
+
+Fix Unreferenced closed WALs that were never written to [#823] [#845] Fixes
issue where failures
+could result in the creation of many files with a header and no data. Recovery
treated these
+as an "empty" files during recovery.
+
+Handle many tablets referencing many WALs [#854] [#860] Reduces the number of
wals that a tserver
+references, this speeds recovery by reducing the number of wals needed during
recovery. When a the
+number of wals referenced by a tserver exceeds a threshold, the tserver will
flush and minor
+compactthe oldest log to limit the number of wal references.
+
+Fix WAL RecoveryLogReader error on failed file [#961] [#1048] If a tserver
fails sorting, a marker
+file is written to the recovery directory. The presence of this marker
prevented any subsequent
+attempts at recovery from succeeding.
+(originally
[ACCUMULO-4861](https://issues.apache.org/jira/browse/ACCUMULO-4861)
+
### Fix ArrayOutOfBounds error when new files are created (affects all
previous versions)
Accumulo maintains a 1-up counter to keep file names and other identifiers
@@ -36,15 +60,132 @@ I0123abc.rf, you are probably at low risk from this bug.
This issue was fixed in pull request [#562]
-### ~Another notable item here~ (affects ~versions~)
+### Stop locking during compaction
+
+Compactions were acquiring the tablet lock between each key value.
+This created unnecessary contention with other operations like scan and
+bulk imports. For {% ghi 1031 %} the the synchronization was removed
+by {% ghi 1032 %}.
+
+### Fixed splitting tablets with files and no data
+
+The split code assumed that if a tablet had files that it had data in
+those files. There are some edge case where this is not true. Updated
+the split code to handle this {% ghi 998 %} {% ghi 999 %} .
+
+### Log when a scan waits a long time for files.
+
+Accumulo has a configurable limit on the max number of files open in a
+tserver for all scans. When too many files are open, scans must wait.
+In {% ghi 978 %} and {% ghi 981 %} scans that wait too long for files
+now log a message.
+
+### Fixed race condition in table existance check.
+
+The Accumulo client code that checks if tables exists had a race
+condition. The race was fixed in {% ghi 768 %} and {% ghi 973 %}
+
+### Support running Mini Accumulo using Java 11
-More description here. This was fixed in [#NUM].
+Mini Accumulo made some assumptions about classloaders that were no
+longer true in Java 11. This caused Mini to fail in Java 11. In
+{% ghi 924 %} Mini was updated to work with Java 11, while still working
+with Java 7 and 8.
-## Other Changes
+### Fixed issue with improperly configured Snappy
+If snappy was configured for a table and the snappy libraries were not
+available on the system then this could cause minor compactions to hang
+forever. In {% ghi 920 %} and {% ghi 925 %} this was fixed and minor
+compactions will proceed when a different compression is configured.
+
+### Handle bad locality group config.
+
+Improperly configured locality groups could cause a tablet to become
+inoperative. This was fixed in {% ghi 819 %} and {% ghi 840 %}.
+
+### Fixed bulk import race condition.
+
+There was a race condition in bulk import that could result in files
+being imported after a bulk import transaction had completed. In the
+worst case these files were already compacted
[accumulo] branch master updated: Update MAC javadoc
This is an automated email from the ASF dual-hosted git repository.
mmiller pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo.git
The following commit(s) were added to refs/heads/master by this push:
new 33317e8 Update MAC javadoc
33317e8 is described below
commit 33317e82c7be0eda993dd5b60cc9987a9251a82c
Author: Mike Miller
AuthorDate: Thu Apr 4 12:09:41 2019 -0400
Update MAC javadoc
---
.../java/org/apache/accumulo/harness/AccumuloClusterHarness.java| 6 --
.../java/org/apache/accumulo/harness/SharedMiniClusterBase.java | 4 +++-
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git
a/test/src/main/java/org/apache/accumulo/harness/AccumuloClusterHarness.java
b/test/src/main/java/org/apache/accumulo/harness/AccumuloClusterHarness.java
index c87d1a3..51708c3 100644
--- a/test/src/main/java/org/apache/accumulo/harness/AccumuloClusterHarness.java
+++ b/test/src/main/java/org/apache/accumulo/harness/AccumuloClusterHarness.java
@@ -57,8 +57,10 @@ import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
/**
- * General Integration-Test base class that provides access to an Accumulo
instance for testing.
- * This instance could be MAC or a standalone instance.
+ * Integration-Test base class that provides a MAC instance per test. WARNING:
This IT type will
+ * setup and teardown an entire cluster for every test annotated with @Test
and is reserved for more
+ * advanced ITs that do crazy things. For more typical, expected behavior of a
cluster see
+ * {@link SharedMiniClusterBase}. This instance can be MAC or a standalone
instance.
*/
@Category(StandaloneCapableClusterTests.class)
public abstract class AccumuloClusterHarness extends AccumuloITBase
diff --git
a/test/src/main/java/org/apache/accumulo/harness/SharedMiniClusterBase.java
b/test/src/main/java/org/apache/accumulo/harness/SharedMiniClusterBase.java
index 4195120..2d2c72f 100644
--- a/test/src/main/java/org/apache/accumulo/harness/SharedMiniClusterBase.java
+++ b/test/src/main/java/org/apache/accumulo/harness/SharedMiniClusterBase.java
@@ -41,7 +41,9 @@ import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
/**
- * Convenience class which starts a single MAC instance for a test to leverage.
+ * Integration-Test base class which starts one MAC for the entire Integration
Test. This IT type is
+ * faster and more geared for testing typical, expected behavior of a cluster.
For more advanced
+ * testing see {@link AccumuloClusterHarness}
*
* There isn't a good way to build this off of the {@link
AccumuloClusterHarness} (as would be the
* logical place) because we need to start the MiniAccumuloCluster in a static
BeforeClass-annotated
