diff --git a/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html b/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html index 2f2e24a..8a42139 100644 --- a/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html +++ b/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html @@ -22,144 +22,6 @@
- -
-
-Status
-
-
-This package is experimental quality software and is only meant to be a base -for future developments. The current implementation offers the following -features: - -
-
-Requirements
-
-
- -Before trying out replication, make sure to review the following requirements: - -
-
-Deployment
-
-
- -The following steps describe how to enable replication from a cluster -to another. -
-<property> - <name>hbase.replication</name> - <value>true</value> -</property>- deploy the files, and then restart HBase if it was running. -
add_peer 'ID' 'CLUSTER_KEY'- The ID is a string, which must not contain a hyphen. To compose the CLUSTER_KEY, use the following template: -
hbase.zookeeper.quorum:hbase.zookeeper.property.clientPort:zookeeper.znode.parent- This will show you the help to setup the replication stream between - both clusters. If both clusters use the same Zookeeper cluster, you have - to use a different zookeeper.znode.parent since they can't - write in the same folder. -
- disable 'your_table'
- alter 'your_table', {NAME => 'family_name', REPLICATION_SCOPE => '1'}
- enable 'your_table'
-
- Currently, a scope of 0 (default) means that it won't be replicated and a
- scope of 1 means it's going to be. In the future, different scope can be
- used for routing policies.
- list_peers(as of version 0.92) -
enable_peer 'ID'-
disable_peer 'ID'-
remove_peer 'ID'-
-Considering 1 rs, with ratio 0.1 -Getting 1 rs from peer cluster # 0 -Choosing peer 10.10.1.49:62020- -In this case it indicates that 1 region server from the slave cluster -was chosen for replication.
-
-
-Verifying Replicated Data
-
-
-Verifying the replicated data on two clusters is easy to do in the shell when -looking only at a few rows, but doing a systematic comparison requires more -computing power. This is why the VerifyReplication MR job was created, it has -to be run on the master cluster and needs to be provided with a peer id (the -one provided when establishing a replication stream) and a table name. Other -options let you specify a time range and specific families. This job's short -name is "verifyrep" and needs to be provided when pointing "hadoop jar" to the -hbase jar. -
- +Cluster replication documentation has been moved to the link:http://hbase.apache.org/book.html#_cluster_replication[Cluster Replication] section of the link:http://hbase.apache.org/book.html[Apache HBase Reference Guide].