accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/2] accumulo git commit: ACCUMULO-3231 Add a readme
Date Fri, 07 Nov 2014 21:01:24 GMT
Repository: accumulo
Updated Branches:
  refs/heads/master 5fdbb8191 -> 5aff1fb7b

ACCUMULO-3231 Add a readme


Branch: refs/heads/master
Commit: 5aff1fb7bbac4fbcaf37121125e076f120c1e50e
Parents: f6af58d
Author: Josh Elser <>
Authored: Fri Nov 7 15:49:41 2014 -0500
Committer: Josh Elser <>
Committed: Fri Nov 7 15:51:53 2014 -0500

 test/system/merkle-replication/README | 65 ++++++++++++++++++++++++++++++
 1 file changed, 65 insertions(+)
diff --git a/test/system/merkle-replication/README b/test/system/merkle-replication/README
new file mode 100644
index 0000000..18100de
--- /dev/null
+++ b/test/system/merkle-replication/README
@@ -0,0 +1,65 @@
+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
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+See the License for the specific language governing permissions and
+limitations under the License.
+Distributed Replication Test
+Ingests random data into a table configured for replication, and then
+verifies that the original table and the replicated table have equivalent
+data using a Merkle tree.
+* Steps to run test
+1. Configure
+    Be sure to set the username/password to connect to Accumulo and
+    the Accumulo instance name and ZooKeepers. The example defaults
+    to using the same instance as the source and destination.
+    The randomness of the generated data can be controlled via some
+    parameters in this file. Note that if deletes are introduced, it
+    is very likely to cause an incorrect verification since the tombstone'ing
+    of that delete will differ on the source and remote due to the order
+    of minor compactions that occur.
+2. Run
+    This script sets up the two instances for replication, creates
+    the tables that will be replicated and adds some splits to them.
+    This is destructive to any existing replication configuration so
+    use it with care on a real instance.
+3. Run
+    Ingests the configured amount of random data into the source
+    table.
+4. Run && on the source instance
+    A tabletserver in the source instance is likely to still be referencing
+    a WAL for a presently online tablet which will prevent that
+    file from being replicated. Stopping the local instance will ensure
+    that all WALs are candidate for replication.
+5. Run
+    This will compute the leaves merkle tree for the source and destination
+    tables and then compute the root hash for both. The root hash
+    is presented to the user.
+    If the root hashes are equal, the test passed; otherwise, the test fails.

View raw message