svn commit: r1177867 - /hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html

[st...@apache.org]

Author: stack
Date: Fri Sep 30 22:29:19 2011
New Revision: 1177867

URL: http://svn.apache.org/viewvc?rev=1177867&view=rev
Log:
HBASE-4517 Document new replication features in 0.92

Modified:
    hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html

Modified: hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html
URL: http://svn.apache.org/viewvc/hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html?rev=1177867&r1=1177866&r2=1177867&view=diff
==============================================================================
--- hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html (original)
+++ hbase/trunk/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html Fri Sep 30 22:29:19 2011
@@ -44,7 +44,9 @@ for future developments. The current imp
 features:
 
 <ol>
-    <li>Master/Slave replication limited to 1 slave cluster. </li>
+    <li>Master/Slave replication.</li>
+    <li>Master/Master replication.</li>
+    <li>Cyclic replication.</li>
     <li>Replication of scoped families in user tables.</li>
     <li>Start/stop replication stream.</li>
     <li>Supports clusters of different sizes.</li>
@@ -74,6 +76,8 @@ Before trying out replication, make sure
     <li>Every table that contains families that are scoped for replication
     should exist on every cluster with the exact same name, same for those
     replicated families.</li>
+    <li>For multiple slaves, Master/Master, or cyclic replication version
+    0.92 or greater is needed.</li>
 </ol>
 
 <p>
@@ -113,6 +117,10 @@ to another.
     scope of 1 means it's going to be. In the future, different scope can be
     used for routing policies.
     </li>
+    <li>To list all configured peers run the following command in the master's
+    shell
+    <pre>list_peers</pre> (as of version 0.92)
+    </li>
 </ol>
 
 You can confirm that your setup works by looking at any region server's log