hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From te...@apache.org
Subject hbase git commit: HBASE-13226 Document enable_table_replication and disable_table_replication shell commands (Ashish Singhi)
Date Fri, 13 Mar 2015 14:07:01 GMT
Repository: hbase
Updated Branches:
  refs/heads/master 6152d36c8 -> fbe732287


HBASE-13226 Document enable_table_replication and disable_table_replication shell commands
(Ashish Singhi)


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/fbe73228
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/fbe73228
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/fbe73228

Branch: refs/heads/master
Commit: fbe7322870fa06406895ea2b4e5b2aae52209e6d
Parents: 6152d36
Author: tedyu <yuzhihong@gmail.com>
Authored: Fri Mar 13 07:06:55 2015 -0700
Committer: tedyu <yuzhihong@gmail.com>
Committed: Fri Mar 13 07:06:55 2015 -0700

----------------------------------------------------------------------
 src/main/asciidoc/_chapters/ops_mgt.adoc | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/fbe73228/src/main/asciidoc/_chapters/ops_mgt.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/_chapters/ops_mgt.adoc b/src/main/asciidoc/_chapters/ops_mgt.adoc
index 584b801..b8018b6 100644
--- a/src/main/asciidoc/_chapters/ops_mgt.adoc
+++ b/src/main/asciidoc/_chapters/ops_mgt.adoc
@@ -1295,14 +1295,8 @@ Instead of SQL statements, entire WALEdits (consisting of multiple
cell inserts
 . All hosts in the source and destination clusters should be reachable to each other.
 . If both clusters use the same ZooKeeper cluster, you must use a different `zookeeper.znode.parent`,
because they cannot write in the same folder.
 . Check to be sure that replication has not been disabled. `hbase.replication` defaults to
`true`.
-. On the source cluster, configure each column family to be replicated by setting its REPLICATION_SCOPE
to 1, using commands such as the following in HBase Shell.
-+
-----
-hbase> disable 'example_table'
-hbase> alter 'example_table', {NAME => 'example_family', REPLICATION_SCOPE => '1'}
-hbase> enable 'example_table'
-----
 . On the source cluster, in HBase Shell, add the destination cluster as a peer, using the
`add_peer` command.
+. On the source cluster, in HBase Shell, enable the table replication, using the `enable_table_replication`
command.
 . Check the logs to see if replication is taking place. If so, you will see messages like
the following, coming from the ReplicationSource.
 ----
 LOG.info("Replicating "+clusterId + " -> " + peerClusterId);
@@ -1320,6 +1314,10 @@ disable_peer <ID>::
   Disable a replication relationship. HBase will no longer send edits to that peer cluster,
but it still keeps track of all the new WALs that it will need to replicate if and when it
is re-enabled. 
 remove_peer <ID>::
   Disable and remove a replication relationship. HBase will no longer send edits to that
peer cluster or keep track of WALs.
+enable_table_replication <TABLE_NAME>::
+  Enable the table replication switch for all it's column families. If the table is not found
in the destination cluster then it will create one with the same name and column families.

+disable_table_replication <TABLE_NAME>::
+  Disable the table replication switch for all it's column families. 
 
 === Verifying Replicated Data
 


Mime
View raw message